Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 464847a0c6051e96409ea5f70990f892e4e9c665b32e8267423baa34dce77906

Tx prefix hash: a310e771fe379c748d663559177f75eefd7cb74762dd8f9cd68819d40e2a61f0
Tx public key: f957b34621dc1ae32e00c90122a644afe5050577b0f4da8412f9b8fceb734346
Timestamp: 1734495052 Timestamp [UCT]: 2024-12-18 04:10:52 Age [y:d:h:m:s]: 00:113:00:10:47
Block: 1177647 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 80529 RingCT/type: yes/0
Extra: 01f957b34621dc1ae32e00c90122a644afe5050577b0f4da8412f9b8fceb7343460211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4a4e2cc6b04c4acd0b4dcd198406fa5d9b89e81607bf6695f0e68a60b1c3e921 0.600000000000 1664020 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": 1177657, "vin": [ { "gen": { "height": 1177647 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4a4e2cc6b04c4acd0b4dcd198406fa5d9b89e81607bf6695f0e68a60b1c3e921" } } ], "extra": [ 1, 249, 87, 179, 70, 33, 220, 26, 227, 46, 0, 201, 1, 34, 166, 68, 175, 229, 5, 5, 119, 176, 244, 218, 132, 18, 249, 184, 252, 235, 115, 67, 70, 2, 17, 0, 0, 0, 4, 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