Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d21bbc4b62cba596c60833b0d6ecd4247af7b87304f9aa92c536f1af4938d41c

Tx prefix hash: 0b3a5046a46296d9f39518781a7029a5378c5c023274e768c43abb1ff92feafe
Tx public key: 519a406168f40dbe5772d5eb8c1a25044a7cfa9cb560c47ff768346bd84d9e2d
Timestamp: 1710607277 Timestamp [UCT]: 2024-03-16 16:41:17 Age [y:d:h:m:s]: 01:234:19:15:19
Block: 979700 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 426480 RingCT/type: yes/0
Extra: 01519a406168f40dbe5772d5eb8c1a25044a7cfa9cb560c47ff768346bd84d9e2d021100000002679a8a81000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f5126a4675c5361d8bbd838fd12ca6fbf3cd06e5b7cbbeab91d1a5093794a590 0.600000000000 1439751 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": 979710, "vin": [ { "gen": { "height": 979700 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f5126a4675c5361d8bbd838fd12ca6fbf3cd06e5b7cbbeab91d1a5093794a590" } } ], "extra": [ 1, 81, 154, 64, 97, 104, 244, 13, 190, 87, 114, 213, 235, 140, 26, 37, 4, 74, 124, 250, 156, 181, 96, 196, 127, 247, 104, 52, 107, 216, 77, 158, 45, 2, 17, 0, 0, 0, 2, 103, 154, 138, 129, 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