Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fa6852a2f3164b081af0c2f3a735f8db194b95133ecb59b58c15793904f22266

Tx prefix hash: 65e93c2580f2f08f8f4d62c6dce598095e831d390a5392547d4828e6f6656ee0
Tx public key: 01d9fd000fa7fa68277279a82f467f4dd5d3d51f0e59a26c4b31c991e37562f6
Timestamp: 1721131131 Timestamp [UCT]: 2024-07-16 11:58:51 Age [y:d:h:m:s]: 00:224:11:51:42
Block: 1066952 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 160313 RingCT/type: yes/0
Extra: 0101d9fd000fa7fa68277279a82f467f4dd5d3d51f0e59a26c4b31c991e37562f602110000000ae914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f03eaf6acc97bcf9cff05347b72548abea542321bbb04a0f0e9b3822a53c5fd8 0.600000000000 1537635 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": 1066962, "vin": [ { "gen": { "height": 1066952 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f03eaf6acc97bcf9cff05347b72548abea542321bbb04a0f0e9b3822a53c5fd8" } } ], "extra": [ 1, 1, 217, 253, 0, 15, 167, 250, 104, 39, 114, 121, 168, 47, 70, 127, 77, 213, 211, 213, 31, 14, 89, 162, 108, 75, 49, 201, 145, 227, 117, 98, 246, 2, 17, 0, 0, 0, 10, 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