Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: db81f6a9730764323a655640ab47d62a05246ed3eab713f78410fcf4642db996

Tx prefix hash: f9f776f892def7d7594774c7dc6ac49fae1f7c0b9f9ef77486112e4625ec0172
Tx public key: 00ef70a19ddb7430f80b4b14997078c1bd5c03fe204dfbbd936f87d71435298a
Timestamp: 1699774955 Timestamp [UCT]: 2023-11-12 07:42:35 Age [y:d:h:m:s]: 02:057:08:35:27
Block: 889890 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 560842 RingCT/type: yes/0
Extra: 0100ef70a19ddb7430f80b4b14997078c1bd5c03fe204dfbbd936f87d71435298a021100000001e6d27f9c000000000000000000

1 output(s) for total of 0.690915630000 dcy

stealth address amount amount idx
00: c89b98586f42407b671dd5cfc25070b9b10713e7d81cd8d0360e8a2f45bdc951 0.690915630000 1345907 of 0

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": 889900, "vin": [ { "gen": { "height": 889890 } } ], "vout": [ { "amount": 690915630, "target": { "key": "c89b98586f42407b671dd5cfc25070b9b10713e7d81cd8d0360e8a2f45bdc951" } } ], "extra": [ 1, 0, 239, 112, 161, 157, 219, 116, 48, 248, 11, 75, 20, 153, 112, 120, 193, 189, 92, 3, 254, 32, 77, 251, 189, 147, 111, 135, 215, 20, 53, 41, 138, 2, 17, 0, 0, 0, 1, 230, 210, 127, 156, 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