Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 03fbd368c2053af44ff21e4bbf99c4da6d7fc69faf5b18afe317f14fa299fe51

Tx prefix hash: fc7f76b935ac8d5af3f43069e5fcf56f5c4ed1c1c9677f152f3a6e1736265d77
Tx public key: 7dc5d69d50f73bba782e6d282259c0feeeb3f4a0fc7be0bf7c02d5f7944cbb9d
Timestamp: 1722019394 Timestamp [UCT]: 2024-07-26 18:43:14 Age [y:d:h:m:s]: 00:281:05:28:13
Block: 1074293 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 200924 RingCT/type: yes/0
Extra: 017dc5d69d50f73bba782e6d282259c0feeeb3f4a0fc7be0bf7c02d5f7944cbb9d02110000000ee914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8a23a07d8f80e3d3275ee61aa7b788122bacd92eb43490294c2cb25b40be7b07 0.600000000000 1546806 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": 1074303, "vin": [ { "gen": { "height": 1074293 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8a23a07d8f80e3d3275ee61aa7b788122bacd92eb43490294c2cb25b40be7b07" } } ], "extra": [ 1, 125, 197, 214, 157, 80, 247, 59, 186, 120, 46, 109, 40, 34, 89, 192, 254, 238, 179, 244, 160, 252, 123, 224, 191, 124, 2, 213, 247, 148, 76, 187, 157, 2, 17, 0, 0, 0, 14, 233, 20, 221, 21, 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