Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3aa4bc718003b84b14f7413c5edd39f95ff9df239dd433a2abaca9a2eadf3eb0

Tx prefix hash: ddbbeb4f86b35f3a73e0c08477dc93ce56adb185e9d732f84197f48b983449cf
Tx public key: 4d544fa16d1a53fdbf428ddaf3b2828a69ca7be53e9e33e21cc59ccd6cf15617
Timestamp: 1626243427 Timestamp [UCT]: 2021-07-14 06:17:07 Age [y:d:h:m:s]: 03:164:09:42:17
Block: 293657 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 888609 RingCT/type: yes/0
Extra: 014d544fa16d1a53fdbf428ddaf3b2828a69ca7be53e9e33e21cc59ccd6cf156170211000001343525d189000000000000000000

1 output(s) for total of 65.315285929000 dcy

stealth address amount amount idx
00: ad297ec7983facdcae99e078f2fa3b2995a8ed4837f3586fe349bd5e68fe50c2 65.315285929000 615233 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": 293667, "vin": [ { "gen": { "height": 293657 } } ], "vout": [ { "amount": 65315285929, "target": { "key": "ad297ec7983facdcae99e078f2fa3b2995a8ed4837f3586fe349bd5e68fe50c2" } } ], "extra": [ 1, 77, 84, 79, 161, 109, 26, 83, 253, 191, 66, 141, 218, 243, 178, 130, 138, 105, 202, 123, 229, 62, 158, 51, 226, 28, 197, 156, 205, 108, 241, 86, 23, 2, 17, 0, 0, 1, 52, 53, 37, 209, 137, 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