Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ed79159ca8f4ed7aad19a12bbd8073d3930e4c509959763a01fab506f5d9620a

Tx prefix hash: 38fd7b31990c9a1a8f7b36342c4190f4a7d760f611f0837be57f078b00fd5139
Tx public key: 5efb9aef13e97aaac392874c495d6ee4cdb88f2af38313d58ee5e3b664a73398
Timestamp: 1730820299 Timestamp [UCT]: 2024-11-05 15:24:59 Age [y:d:h:m:s]: 00:001:17:30:46
Block: 1147174 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1246 RingCT/type: yes/0
Extra: 015efb9aef13e97aaac392874c495d6ee4cdb88f2af38313d58ee5e3b664a73398021100000009007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 917d706c23d83c02e517d884e923b3fa8cfcf8db1047a2596bfcb960203d93c0 0.600000000000 1631867 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": 1147184, "vin": [ { "gen": { "height": 1147174 } } ], "vout": [ { "amount": 600000000, "target": { "key": "917d706c23d83c02e517d884e923b3fa8cfcf8db1047a2596bfcb960203d93c0" } } ], "extra": [ 1, 94, 251, 154, 239, 19, 233, 122, 170, 195, 146, 135, 76, 73, 93, 110, 228, 205, 184, 143, 42, 243, 131, 19, 213, 142, 229, 227, 182, 100, 167, 51, 152, 2, 17, 0, 0, 0, 9, 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