Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f74fc8edcbc591a57bcf1ae43d71e7e7af733b2846176d8323009519f4a1082b

Tx prefix hash: 468ab140e4bbb25783ef3778d910beca1ac75ec882414c69ce29d867d1756395
Tx public key: faa1f832f986585e44b070e33a5b145487d26dc1cfd23efe5472a37ed05b7d6f
Timestamp: 1682330670 Timestamp [UCT]: 2023-04-24 10:04:30 Age [y:d:h:m:s]: 01:263:21:37:59
Block: 745507 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 450087 RingCT/type: yes/0
Extra: 01faa1f832f986585e44b070e33a5b145487d26dc1cfd23efe5472a37ed05b7d6f02110000000133af99f4000000000000000000

1 output(s) for total of 2.078863835000 dcy

stealth address amount amount idx
00: a77d041295adf8d9dd9fea90f9b559bb503b251bb3a79d56275a18a407b0d2c4 2.078863835000 1192964 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": 745517, "vin": [ { "gen": { "height": 745507 } } ], "vout": [ { "amount": 2078863835, "target": { "key": "a77d041295adf8d9dd9fea90f9b559bb503b251bb3a79d56275a18a407b0d2c4" } } ], "extra": [ 1, 250, 161, 248, 50, 249, 134, 88, 94, 68, 176, 112, 227, 58, 91, 20, 84, 135, 210, 109, 193, 207, 210, 62, 254, 84, 114, 163, 126, 208, 91, 125, 111, 2, 17, 0, 0, 0, 1, 51, 175, 153, 244, 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