Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 02cc3782555c17905d1cefa9c5e62683317d424304b0ed59426e37230449d4f5

Tx prefix hash: 4cd6edf69e4683c0a5cb5cacddfe11e1dd62a180306f8e0aee561b95b080f0e6
Tx public key: 731448d51b20c7bc214e7fc9431cd53b3e407b8dc991b6ca36912fe261fc3f34
Timestamp: 1711843185 Timestamp [UCT]: 2024-03-30 23:59:45 Age [y:d:h:m:s]: 01:077:06:12:09
Block: 989950 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 316103 RingCT/type: yes/0
Extra: 01731448d51b20c7bc214e7fc9431cd53b3e407b8dc991b6ca36912fe261fc3f340211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 92e44b2b8594cb1f8d9cd98a2deb3bffd85e52e001201925c4db22d372fd449c 0.600000000000 1450268 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": 989960, "vin": [ { "gen": { "height": 989950 } } ], "vout": [ { "amount": 600000000, "target": { "key": "92e44b2b8594cb1f8d9cd98a2deb3bffd85e52e001201925c4db22d372fd449c" } } ], "extra": [ 1, 115, 20, 72, 213, 27, 32, 199, 188, 33, 78, 127, 201, 67, 28, 213, 59, 62, 64, 123, 141, 201, 145, 182, 202, 54, 145, 47, 226, 97, 252, 63, 52, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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