Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cc8944bdcd58a42b728cce61db949a0ca4cd06abb37d1168ac7909b8e86cb58f

Tx prefix hash: 22059ee2b5c42ac78d04e0c14b0852115664ec5117d05155d413122bba40a69f
Tx public key: a7e5b547e15c3c6c3a707e324acb0c94b9ac03f33b2d0f3088002cfdc968552a
Timestamp: 1730465763 Timestamp [UCT]: 2024-11-01 12:56:03 Age [y:d:h:m:s]: 00:141:21:01:16
Block: 1144240 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 101235 RingCT/type: yes/0
Extra: 01a7e5b547e15c3c6c3a707e324acb0c94b9ac03f33b2d0f3088002cfdc968552a0211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ff3787e8a61ec20d8787b75b2f1c3adde43deef48387ca9915ea89bb68bc480e 0.600000000000 1628391 of 15

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": 1144250, "vin": [ { "gen": { "height": 1144240 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ff3787e8a61ec20d8787b75b2f1c3adde43deef48387ca9915ea89bb68bc480e" } } ], "extra": [ 1, 167, 229, 181, 71, 225, 92, 60, 108, 58, 112, 126, 50, 74, 203, 12, 148, 185, 172, 3, 243, 59, 45, 15, 48, 136, 0, 44, 253, 201, 104, 85, 42, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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