Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3ead3ee8a2fe432dcb1663c6d50cae570438838662712ef0b5c8be39ed41f224

Tx prefix hash: fc7424c339a5494f7b63b5ba95e99d3e809619153a17c15851300dcd17be7bd9
Tx public key: 9aa33b8adfe38940d4fe7cc4445e1a9e25ed86e1d00f1014b4314de49b9ca690
Timestamp: 1645835425 Timestamp [UCT]: 2022-02-26 00:30:25 Age [y:d:h:m:s]: 03:017:06:37:01
Block: 446546 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 792408 RingCT/type: yes/0
Extra: 019aa33b8adfe38940d4fe7cc4445e1a9e25ed86e1d00f1014b4314de49b9ca690021100000026d3fcec30000000000000000000

1 output(s) for total of 20.342672893000 dcy

stealth address amount amount idx
00: 858feb9a2d9f9441a6eda51b55625616110857e676a4de24f4f91fa6aca77a11 20.342672893000 860463 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": 446556, "vin": [ { "gen": { "height": 446546 } } ], "vout": [ { "amount": 20342672893, "target": { "key": "858feb9a2d9f9441a6eda51b55625616110857e676a4de24f4f91fa6aca77a11" } } ], "extra": [ 1, 154, 163, 59, 138, 223, 227, 137, 64, 212, 254, 124, 196, 68, 94, 26, 158, 37, 237, 134, 225, 208, 15, 16, 20, 180, 49, 77, 228, 155, 156, 166, 144, 2, 17, 0, 0, 0, 38, 211, 252, 236, 48, 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