Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e01597e2e4d1cd63c88c2260842124372fc353fda79e08dcb571c574b6e039c0

Tx prefix hash: b6931e203db5130b16445fa5d35f12d21d700212d0c71cc2b9fb70fab59f6139
Tx public key: 7d172defc407a3ba4e786b2131919cf67996933d56fbd3d59aa3b8cee994d72f
Timestamp: 1712756057 Timestamp [UCT]: 2024-04-10 13:34:17 Age [y:d:h:m:s]: 01:036:15:12:13
Block: 997475 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 287176 RingCT/type: yes/0
Extra: 017d172defc407a3ba4e786b2131919cf67996933d56fbd3d59aa3b8cee994d72f02110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3ecf06fee052deab7a2cd4e2da909a02c8d923f67c97cac86e5801f0bda33f43 0.600000000000 1457907 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": 997485, "vin": [ { "gen": { "height": 997475 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3ecf06fee052deab7a2cd4e2da909a02c8d923f67c97cac86e5801f0bda33f43" } } ], "extra": [ 1, 125, 23, 45, 239, 196, 7, 163, 186, 78, 120, 107, 33, 49, 145, 156, 246, 121, 150, 147, 61, 86, 251, 211, 213, 154, 163, 184, 206, 233, 148, 215, 47, 2, 17, 0, 0, 0, 4, 82, 212, 126, 148, 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