Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c6f5afdbc4b2fead0492db5e4e29559afb71c658d4452f2a4b27bd42478c1902

Tx prefix hash: 65d6eca7edc335b35880615c2f284e09717105a48f266c119890ac3e7a25cde6
Tx public key: f546042e2e36508c9c89cb809da51ebcd1abf2f21e9ea8c7560a02a7664d1707
Timestamp: 1740242385 Timestamp [UCT]: 2025-02-22 16:39:45 Age [y:d:h:m:s]: 00:228:20:08:02
Block: 1224907 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 161262 RingCT/type: yes/0
Extra: 01f546042e2e36508c9c89cb809da51ebcd1abf2f21e9ea8c7560a02a7664d170702110000000c007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3137435c0613bff6b8a8ced6430093b98d2b3640999c1465926c761a3b764dd5 0.600000000000 1711770 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": 1224917, "vin": [ { "gen": { "height": 1224907 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3137435c0613bff6b8a8ced6430093b98d2b3640999c1465926c761a3b764dd5" } } ], "extra": [ 1, 245, 70, 4, 46, 46, 54, 80, 140, 156, 137, 203, 128, 157, 165, 30, 188, 209, 171, 242, 242, 30, 158, 168, 199, 86, 10, 2, 167, 102, 77, 23, 7, 2, 17, 0, 0, 0, 12, 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