Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 94b464c615eafdba86c5fb6b22794922a1ffa47a493fa51e1c252e4884f301ad

Tx prefix hash: 2b53b793d71c9e0d768403227f74ded4461fb9e00867b1836bbb3273d4672a33
Tx public key: a658b5c6763a8e801016792fdc47cfc42ceea8737f1c6be8f0e59610c7da74f2
Timestamp: 1653897332 Timestamp [UCT]: 2022-05-30 07:55:32 Age [y:d:h:m:s]: 02:216:21:03:56
Block: 511957 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 675690 RingCT/type: yes/0
Extra: 01a658b5c6763a8e801016792fdc47cfc42ceea8737f1c6be8f0e59610c7da74f2021100000013c9067537000000000000000000

1 output(s) for total of 12.350203779000 dcy

stealth address amount amount idx
00: ecc2bc58964ac0d6cc59fd7b4658dd3019918a4e90ecff455dd1964e1a554b65 12.350203779000 938522 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": 511967, "vin": [ { "gen": { "height": 511957 } } ], "vout": [ { "amount": 12350203779, "target": { "key": "ecc2bc58964ac0d6cc59fd7b4658dd3019918a4e90ecff455dd1964e1a554b65" } } ], "extra": [ 1, 166, 88, 181, 198, 118, 58, 142, 128, 16, 22, 121, 47, 220, 71, 207, 196, 44, 238, 168, 115, 127, 28, 107, 232, 240, 229, 150, 16, 199, 218, 116, 242, 2, 17, 0, 0, 0, 19, 201, 6, 117, 55, 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