Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 070a946b9102998806a9dbc851ec583386051eee6f52ef216f4efde84d3d5775

Tx prefix hash: c0e818bb4dd1ba71546fe482aad848239eb414d887535c4b0f3c89a680dae293
Tx public key: d6b27db92b7eb5bee801c960af91b26d72c03e806f27c3dec258cef16932f1fa
Timestamp: 1730765223 Timestamp [UCT]: 2024-11-05 00:07:03 Age [y:d:h:m:s]: 00:156:22:50:04
Block: 1146711 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 112012 RingCT/type: yes/0
Extra: 01d6b27db92b7eb5bee801c960af91b26d72c03e806f27c3dec258cef16932f1fa021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 52b41c9f0f91195354f48d909b706572896e6d2870311a11175923bde0e0e8cb 0.600000000000 1631402 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": 1146721, "vin": [ { "gen": { "height": 1146711 } } ], "vout": [ { "amount": 600000000, "target": { "key": "52b41c9f0f91195354f48d909b706572896e6d2870311a11175923bde0e0e8cb" } } ], "extra": [ 1, 214, 178, 125, 185, 43, 126, 181, 190, 232, 1, 201, 96, 175, 145, 178, 109, 114, 192, 62, 128, 111, 39, 195, 222, 194, 88, 206, 241, 105, 50, 241, 250, 2, 17, 0, 0, 0, 5, 0, 127, 151, 138, 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