Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8cfb5c10f0e35d1682ac723fd351cb062cfec5b25489d628e66329b42ef95b55

Tx prefix hash: cd4d1230960be5950705b6d2ddc28a1f5da97ddb7717bbe7c8d58cc9710724c3
Tx public key: ca20d5ab0013b41f1879025adde1d6b13e380856314edd6fa2b71c22072772f9
Timestamp: 1710623748 Timestamp [UCT]: 2024-03-16 21:15:48 Age [y:d:h:m:s]: 00:325:20:58:19
Block: 979845 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 232965 RingCT/type: yes/0
Extra: 01ca20d5ab0013b41f1879025adde1d6b13e380856314edd6fa2b71c22072772f90211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 78a2cb536c75eae13eba291ae7bc7e53d223c34f9a9b42981a39f88bd8d7fad8 0.600000000000 1439900 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": 979855, "vin": [ { "gen": { "height": 979845 } } ], "vout": [ { "amount": 600000000, "target": { "key": "78a2cb536c75eae13eba291ae7bc7e53d223c34f9a9b42981a39f88bd8d7fad8" } } ], "extra": [ 1, 202, 32, 213, 171, 0, 19, 180, 31, 24, 121, 2, 90, 221, 225, 214, 177, 62, 56, 8, 86, 49, 78, 221, 111, 162, 183, 28, 34, 7, 39, 114, 249, 2, 17, 0, 0, 0, 5, 122, 156, 244, 199, 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