Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d2df691050fc1e913174f6d1a7f9f75dfa0ab4380fd331096ebd17a020f43414

Tx prefix hash: b1e67413d1dbc609ca3d1147cc21cbf399b352911edfed7d407b5717b038a386
Tx public key: 411dcd07f8bbf6e259ae21aa2a05262079327353815489a218166d89562c52e7
Timestamp: 1724858853 Timestamp [UCT]: 2024-08-28 15:27:33 Age [y:d:h:m:s]: 01:067:23:28:33
Block: 1097838 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 307019 RingCT/type: yes/0
Extra: 01411dcd07f8bbf6e259ae21aa2a05262079327353815489a218166d89562c52e702110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2fbc03b5827724bc05e006cb30b7b5cc21d327b6fa806f344ed44f902ce03edb 0.600000000000 1573345 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": 1097848, "vin": [ { "gen": { "height": 1097838 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2fbc03b5827724bc05e006cb30b7b5cc21d327b6fa806f344ed44f902ce03edb" } } ], "extra": [ 1, 65, 29, 205, 7, 248, 187, 246, 226, 89, 174, 33, 170, 42, 5, 38, 32, 121, 50, 115, 83, 129, 84, 137, 162, 24, 22, 109, 137, 86, 44, 82, 231, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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