Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 594f819a8a9141f8ed33119c47d32c272eb495d8cfa776d2d58095f3097ca1aa

Tx prefix hash: c9ba37daf862107f62d48ed51505ed5fc92bf34b4a89444e1b1c3ae3f3a3af43
Tx public key: fbd251b52c79678a5d32a94424a6aaf8b88486b96c2e25b231004813cf2f1fe2
Timestamp: 1718366166 Timestamp [UCT]: 2024-06-14 11:56:06 Age [y:d:h:m:s]: 01:146:05:17:32
Block: 1044019 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 363052 RingCT/type: yes/0
Extra: 01fbd251b52c79678a5d32a94424a6aaf8b88486b96c2e25b231004813cf2f1fe202110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b0f3e189246ef6b3e7ba0840da552b5d5bf87ba651940209b9170058ff505810 0.600000000000 1513212 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": 1044029, "vin": [ { "gen": { "height": 1044019 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b0f3e189246ef6b3e7ba0840da552b5d5bf87ba651940209b9170058ff505810" } } ], "extra": [ 1, 251, 210, 81, 181, 44, 121, 103, 138, 93, 50, 169, 68, 36, 166, 170, 248, 184, 132, 134, 185, 108, 46, 37, 178, 49, 0, 72, 19, 207, 47, 31, 226, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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