Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: daf8f0306896024a398baa89cb115c9dcca0f2384d8ab3dfd0a1347017baf3be

Tx prefix hash: e977c3921a9394c46ec5c33832cd97478337eb85dd180037b4b6e41add6b37c7
Tx public key: df12727ff4e96dbf5696f8b554344fe1584f7286c416e9b2b243408e5f7a6d6f
Timestamp: 1706492743 Timestamp [UCT]: 2024-01-29 01:45:43 Age [y:d:h:m:s]: 01:134:18:54:56
Block: 945541 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 357457 RingCT/type: yes/0
Extra: 01df12727ff4e96dbf5696f8b554344fe1584f7286c416e9b2b243408e5f7a6d6f02110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b4fdee86089301c49b080a301029e670b5ed9eb8d3c37f42cdbd92ccfac00b0d 0.600000000000 1403857 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 945551, "vin": [ { "gen": { "height": 945541 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b4fdee86089301c49b080a301029e670b5ed9eb8d3c37f42cdbd92ccfac00b0d" } } ], "extra": [ 1, 223, 18, 114, 127, 244, 233, 109, 191, 86, 150, 248, 181, 84, 52, 79, 225, 88, 79, 114, 134, 196, 22, 233, 178, 178, 67, 64, 142, 95, 122, 109, 111, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8