Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 17d2dd5eac929ca21d5276413aada5fbca7e347d105fab268ccfc15e66f4e44a

Tx prefix hash: bde38538365876384cc7d96f1bff72fe62da18451e889dc2d5d49bb7b2a8d93a
Tx public key: faf125b8f29a4b7414065e88cd0d7df4b8171a28ce6ea38005699e1233bcc5e7
Timestamp: 1736425277 Timestamp [UCT]: 2025-01-09 12:21:17 Age [y:d:h:m:s]: 00:161:00:42:31
Block: 1193593 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 114780 RingCT/type: yes/0
Extra: 01faf125b8f29a4b7414065e88cd0d7df4b8171a28ce6ea38005699e1233bcc5e70211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f8173ff6668dc09848dcc45fadfdcb1567e64d0b85802e5de67ebfabd9c11371 0.600000000000 1680156 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": 1193603, "vin": [ { "gen": { "height": 1193593 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f8173ff6668dc09848dcc45fadfdcb1567e64d0b85802e5de67ebfabd9c11371" } } ], "extra": [ 1, 250, 241, 37, 184, 242, 154, 75, 116, 20, 6, 94, 136, 205, 13, 125, 244, 184, 23, 26, 40, 206, 110, 163, 128, 5, 105, 158, 18, 51, 188, 197, 231, 2, 17, 0, 0, 0, 5, 31, 10, 83, 235, 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