Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e12f2a30f72dab54d708cfd19bd3a3b3750ca1798d34aff3400e4672304e6da9

Tx prefix hash: 3443443fbbe1057cfbef5789a8c5580f52b0c44c5072eedc04af040c0fe5d681
Tx public key: cefde8a6c6e9a88df6d28a7f8abd74dcb1774fee4a354127d61b98ad8d375763
Timestamp: 1700714031 Timestamp [UCT]: 2023-11-23 04:33:51 Age [y:d:h:m:s]: 01:155:02:18:57
Block: 897666 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 372030 RingCT/type: yes/0
Extra: 01cefde8a6c6e9a88df6d28a7f8abd74dcb1774fee4a354127d61b98ad8d375763021100000003faf35c9c000000000000000000

1 output(s) for total of 0.651118283000 dcy

stealth address amount amount idx
00: 06d4cdb65a06d9e93b9b5a9dd3a16b6f525ab4b5008ab20b080a781454e2024e 0.651118283000 1354051 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": 897676, "vin": [ { "gen": { "height": 897666 } } ], "vout": [ { "amount": 651118283, "target": { "key": "06d4cdb65a06d9e93b9b5a9dd3a16b6f525ab4b5008ab20b080a781454e2024e" } } ], "extra": [ 1, 206, 253, 232, 166, 198, 233, 168, 141, 246, 210, 138, 127, 138, 189, 116, 220, 177, 119, 79, 238, 74, 53, 65, 39, 214, 27, 152, 173, 141, 55, 87, 99, 2, 17, 0, 0, 0, 3, 250, 243, 92, 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