Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 86acbbde358c17a86be57c587a6bc3cd74c508d3b3b9e56b92af3d598603eb4b

Tx prefix hash: fc2bde7fe09d84c1e5dd44979d3e4d7008b28a38b08f2ade84f5666b2c70e44e
Tx public key: a39d06f33d0a4b04f87291a08bba5e6d423af34649bef14973e93298c2dfd6fa
Timestamp: 1648226252 Timestamp [UCT]: 2022-03-25 16:37:32 Age [y:d:h:m:s]: 02:327:07:59:28
Block: 466216 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 753226 RingCT/type: yes/0
Extra: 01a39d06f33d0a4b04f87291a08bba5e6d423af34649bef14973e93298c2dfd6fa021100000006a272b9cb000000000000000000

1 output(s) for total of 17.507861870000 dcy

stealth address amount amount idx
00: c9a5fcc8876fd64c8966a9906b34c4521b5b40e4f34e8e2d4e82cfd69a91e1e3 17.507861870000 884489 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": 466226, "vin": [ { "gen": { "height": 466216 } } ], "vout": [ { "amount": 17507861870, "target": { "key": "c9a5fcc8876fd64c8966a9906b34c4521b5b40e4f34e8e2d4e82cfd69a91e1e3" } } ], "extra": [ 1, 163, 157, 6, 243, 61, 10, 75, 4, 248, 114, 145, 160, 139, 186, 94, 109, 66, 58, 243, 70, 73, 190, 241, 73, 115, 233, 50, 152, 194, 223, 214, 250, 2, 17, 0, 0, 0, 6, 162, 114, 185, 203, 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