Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7cc9a8b3ffc37012519419a5406472c426bdf319d446b98352fd0869a7ff2c57

Tx prefix hash: 0e0f08bf56b75a9f43a392e5e3e26436edcf38471e554b4a9760cf23f69cd8d2
Tx public key: fe1a0e2137e97e1c6dddda281539aaa0714d38cc595c84eb2b4a972b0e413aa3
Timestamp: 1727636618 Timestamp [UCT]: 2024-09-29 19:03:38 Age [y:d:h:m:s]: 00:261:15:49:51
Block: 1120863 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 186747 RingCT/type: yes/0
Extra: 01fe1a0e2137e97e1c6dddda281539aaa0714d38cc595c84eb2b4a972b0e413aa3021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a06971987c0cc391f0df117e55181d506f915806dfc5b0de9edcc3dd6a506310 0.600000000000 1602934 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": 1120873, "vin": [ { "gen": { "height": 1120863 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a06971987c0cc391f0df117e55181d506f915806dfc5b0de9edcc3dd6a506310" } } ], "extra": [ 1, 254, 26, 14, 33, 55, 233, 126, 28, 109, 221, 218, 40, 21, 57, 170, 160, 113, 77, 56, 204, 89, 92, 132, 235, 43, 74, 151, 43, 14, 65, 58, 163, 2, 17, 0, 0, 0, 6, 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