Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 831d7ef77c94354bc961264632310b3432d251db522b2629d1042b767be01654

Tx prefix hash: 38caedc8524ed6972e2b47f041db8ec245685e63f68576c4aae6eae71c6f3a17
Tx public key: d8f7f1fe2336d0a3ea48aa43797a0d4a4519d1f4cdd8392c32e689f8af58ce2b
Timestamp: 1732937191 Timestamp [UCT]: 2024-11-30 03:26:31 Age [y:d:h:m:s]: 00:119:03:57:04
Block: 1164714 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 84962 RingCT/type: yes/0
Extra: 01d8f7f1fe2336d0a3ea48aa43797a0d4a4519d1f4cdd8392c32e689f8af58ce2b021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9cbf4047dc3f8b13855648652d8dfd9f1a19957fdc26c4ac3d98a94f1f1c1caa 0.600000000000 1650389 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": 1164724, "vin": [ { "gen": { "height": 1164714 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9cbf4047dc3f8b13855648652d8dfd9f1a19957fdc26c4ac3d98a94f1f1c1caa" } } ], "extra": [ 1, 216, 247, 241, 254, 35, 54, 208, 163, 234, 72, 170, 67, 121, 122, 13, 74, 69, 25, 209, 244, 205, 216, 57, 44, 50, 230, 137, 248, 175, 88, 206, 43, 2, 17, 0, 0, 0, 4, 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