Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 99d3e10c80cbd8e8c15893596de1b20446d1aeb8d73b20ffa30a574d8657644b

Tx prefix hash: c3acdd8fb73e0cc5263e25345cc5aac8c12dbafea9a1e1e8abfd78274f873e1d
Tx public key: 29c88807808fde3088aa10a47bfa6665b60668d23c5de369eac4550aed98837f
Timestamp: 1684821610 Timestamp [UCT]: 2023-05-23 06:00:10 Age [y:d:h:m:s]: 01:237:16:51:04
Block: 766164 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 431312 RingCT/type: yes/0
Extra: 0129c88807808fde3088aa10a47bfa6665b60668d23c5de369eac4550aed98837f02110000000175e3f0e9000000000000000000

1 output(s) for total of 1.775745806000 dcy

stealth address amount amount idx
00: a9d436bdd786ef14a7827e019a63e4d0c459bcaf0cb5dceb8b28f12083e89d59 1.775745806000 1215185 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": 766174, "vin": [ { "gen": { "height": 766164 } } ], "vout": [ { "amount": 1775745806, "target": { "key": "a9d436bdd786ef14a7827e019a63e4d0c459bcaf0cb5dceb8b28f12083e89d59" } } ], "extra": [ 1, 41, 200, 136, 7, 128, 143, 222, 48, 136, 170, 16, 164, 123, 250, 102, 101, 182, 6, 104, 210, 60, 93, 227, 105, 234, 196, 85, 10, 237, 152, 131, 127, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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