Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b3000085dc33e2f0dd75e0445eddf4324caca7f9c7fe59ce36b5b9b33e001a64

Tx prefix hash: 8cc0a19be6de43c72ae0a5e392d0a5aa407fae8c16cf45c5a666fb5cd07f50ef
Tx public key: 0a7774e95be59561e16c79e8624817324a2db2c3ebd97aee06e8f33761913d64
Timestamp: 1722301032 Timestamp [UCT]: 2024-07-30 00:57:12 Age [y:d:h:m:s]: 00:250:11:27:03
Block: 1076630 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 178913 RingCT/type: yes/0
Extra: 010a7774e95be59561e16c79e8624817324a2db2c3ebd97aee06e8f33761913d6402110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 94b41fbaeb01ba726620b351f3d9fd1ae57e2109325aaf95c3aeaf5c3fa3ffad 0.600000000000 1549169 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": 1076640, "vin": [ { "gen": { "height": 1076630 } } ], "vout": [ { "amount": 600000000, "target": { "key": "94b41fbaeb01ba726620b351f3d9fd1ae57e2109325aaf95c3aeaf5c3fa3ffad" } } ], "extra": [ 1, 10, 119, 116, 233, 91, 229, 149, 97, 225, 108, 121, 232, 98, 72, 23, 50, 74, 45, 178, 195, 235, 217, 122, 238, 6, 232, 243, 55, 97, 145, 61, 100, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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