Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 201e45c1107f05aebafe38b669f92c533956b1c15df65f4ea1ce412bcc205f5f

Tx prefix hash: e168d8d2801481782de58571efdb51c56036e6c7d59c335e60e00020074077c7
Tx public key: d19d2be375e12ada570df1d4d858fca213a415aa8d0d7da61f24c38c37a8eb37
Timestamp: 1732333270 Timestamp [UCT]: 2024-11-23 03:41:10 Age [y:d:h:m:s]: 00:000:18:16:45
Block: 1159703 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 544 RingCT/type: yes/0
Extra: 01d19d2be375e12ada570df1d4d858fca213a415aa8d0d7da61f24c38c37a8eb37021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ad1053236611de42d5554c05078c58d1d55564b57b373c9cb7061ace4c723e00 0.600000000000 1645342 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": 1159713, "vin": [ { "gen": { "height": 1159703 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ad1053236611de42d5554c05078c58d1d55564b57b373c9cb7061ace4c723e00" } } ], "extra": [ 1, 209, 157, 43, 227, 117, 225, 42, 218, 87, 13, 241, 212, 216, 88, 252, 162, 19, 164, 21, 170, 141, 13, 125, 166, 31, 36, 195, 140, 55, 168, 235, 55, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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