Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 613bb12bdee84ca272916915fcff228c8b5da6b98c08b82d86ebbf67665b5e25

Tx prefix hash: 7553b53fc38c5cc94bd2713dabd505cf5af26a196a3de99c751d85234def7799
Tx public key: 49d0c9b823ada9380fb01db6e106e3a642fe8fdb451b3650db69152d1e08f6db
Timestamp: 1702720386 Timestamp [UCT]: 2023-12-16 09:53:06 Age [y:d:h:m:s]: 01:111:06:34:21
Block: 914298 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 340662 RingCT/type: yes/0
Extra: 0149d0c9b823ada9380fb01db6e106e3a642fe8fdb451b3650db69152d1e08f6db021100000003faf35c9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 635a7f2816f00b2238f3ba73d927d97724a9c58f9e6224e08bf5ea9b2f3851e1 0.600000000000 1371594 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": 914308, "vin": [ { "gen": { "height": 914298 } } ], "vout": [ { "amount": 600000000, "target": { "key": "635a7f2816f00b2238f3ba73d927d97724a9c58f9e6224e08bf5ea9b2f3851e1" } } ], "extra": [ 1, 73, 208, 201, 184, 35, 173, 169, 56, 15, 176, 29, 182, 225, 6, 227, 166, 66, 254, 143, 219, 69, 27, 54, 80, 219, 105, 21, 45, 30, 8, 246, 219, 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