Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2eae64209f9a7905bb0a6761bd0126e491eb28b495c3a26a412e0eb9bceb7354

Tx prefix hash: 555655a18f0631cd65b4eb8a853a0e350d16d64c36092ac98a16deae5d2b7078
Tx public key: b485ab8f2e01b840e936a8fce2cd09caead7d2474a75b5be47c4aeb707512070
Timestamp: 1728389509 Timestamp [UCT]: 2024-10-08 12:11:49 Age [y:d:h:m:s]: 00:199:20:03:58
Block: 1127112 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 142623 RingCT/type: yes/0
Extra: 01b485ab8f2e01b840e936a8fce2cd09caead7d2474a75b5be47c4aeb707512070021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6687b1a549b6cbad05cf387acdddc6d268af1b4cbad69fa851d1bc74a58d5911 0.600000000000 1609911 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": 1127122, "vin": [ { "gen": { "height": 1127112 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6687b1a549b6cbad05cf387acdddc6d268af1b4cbad69fa851d1bc74a58d5911" } } ], "extra": [ 1, 180, 133, 171, 143, 46, 1, 184, 64, 233, 54, 168, 252, 226, 205, 9, 202, 234, 215, 210, 71, 74, 117, 181, 190, 71, 196, 174, 183, 7, 81, 32, 112, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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