Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 675949046a4d0cbc003e58d207d017f8b1b642461382a175e4bee7dab8c4e8f0

Tx prefix hash: b8c74d21f409d138d6553b1d61784d6a7e91aafbdefa5fec02180d29ef218bfc
Tx public key: 143f87a40caa24a0212d85e74c0076038dea7a2cfab79c64460ef06ab6b92f20
Timestamp: 1714083094 Timestamp [UCT]: 2024-04-25 22:11:34 Age [y:d:h:m:s]: 00:305:16:02:52
Block: 1008493 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 218495 RingCT/type: yes/0
Extra: 01143f87a40caa24a0212d85e74c0076038dea7a2cfab79c64460ef06ab6b92f2002110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ae0c9385be7e92da1c8fb2e5c81d8a6f113a78563ad048e851bbf3b4df242591 0.600000000000 1469963 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": 1008503, "vin": [ { "gen": { "height": 1008493 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ae0c9385be7e92da1c8fb2e5c81d8a6f113a78563ad048e851bbf3b4df242591" } } ], "extra": [ 1, 20, 63, 135, 164, 12, 170, 36, 160, 33, 45, 133, 231, 76, 0, 118, 3, 141, 234, 122, 44, 250, 183, 156, 100, 70, 14, 240, 106, 182, 185, 47, 32, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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