Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2a63433e1cedeede88e5b6af04b3684276333a4843887c135c82c4f8e9ec1c66

Tx prefix hash: 00178233213d5d34e74fd4c7c98d262f1956c74f22cca0786ee667bcbc4738ac
Tx public key: b3c10b05dad562622ecd70e5e6ac1ee9ae03e9193f68c479b85f193d52011b15
Timestamp: 1646881477 Timestamp [UCT]: 2022-03-10 03:04:37 Age [y:d:h:m:s]: 03:004:13:12:09
Block: 455123 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 783401 RingCT/type: yes/0
Extra: 01b3c10b05dad562622ecd70e5e6ac1ee9ae03e9193f68c479b85f193d52011b15021100000001c9067537000000000000000000

1 output(s) for total of 19.054117618000 dcy

stealth address amount amount idx
00: 6f5309357a3d0aa22b5d3016c9a0e6f62d17730459110de09e2b175131ea0e1a 19.054117618000 870900 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": 455133, "vin": [ { "gen": { "height": 455123 } } ], "vout": [ { "amount": 19054117618, "target": { "key": "6f5309357a3d0aa22b5d3016c9a0e6f62d17730459110de09e2b175131ea0e1a" } } ], "extra": [ 1, 179, 193, 11, 5, 218, 213, 98, 98, 46, 205, 112, 229, 230, 172, 30, 233, 174, 3, 233, 25, 63, 104, 196, 121, 184, 95, 25, 61, 82, 1, 27, 21, 2, 17, 0, 0, 0, 1, 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