Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5e65b4027e1ce07a1bd0ac895e792f49699640bf57e1a3e2c8cd26fec2a8325c

Tx prefix hash: 4940b7ae1b37e3c0b536f027160428ab0c1f3c890d4665e198bcaa4b6e83ffed
Tx public key: bc15474554d2cba846812416ba0d1ae3b983366f66f3f7d5699c643310118cda
Timestamp: 1707593957 Timestamp [UCT]: 2024-02-10 19:39:17 Age [y:d:h:m:s]: 01:132:03:26:42
Block: 954696 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 355359 RingCT/type: yes/0
Extra: 01bc15474554d2cba846812416ba0d1ae3b983366f66f3f7d5699c643310118cda0211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0e3d9d788993555da8d98278c87e79a7d7cdf7ed5df118447c92d4d189131563 0.600000000000 1413978 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": 954706, "vin": [ { "gen": { "height": 954696 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0e3d9d788993555da8d98278c87e79a7d7cdf7ed5df118447c92d4d189131563" } } ], "extra": [ 1, 188, 21, 71, 69, 84, 210, 203, 168, 70, 129, 36, 22, 186, 13, 26, 227, 185, 131, 54, 111, 102, 243, 247, 213, 105, 156, 100, 51, 16, 17, 140, 218, 2, 17, 0, 0, 0, 3, 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