Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 449f9a2723d6af53f6196c20a865d7a7a9ef2eb505817290df519ed73a8e5d4f

Tx prefix hash: 4d0b36371ef3b65956f58c06220984cb36a3c93a754d90ab77061713df50e126
Tx public key: 2f79cf9ba24c852e353f94a3684aeff0918312ac0e1b7baa3269eb329369ebf6
Timestamp: 1727094608 Timestamp [UCT]: 2024-09-23 12:30:08 Age [y:d:h:m:s]: 00:224:17:18:03
Block: 1116379 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 160426 RingCT/type: yes/0
Extra: 012f79cf9ba24c852e353f94a3684aeff0918312ac0e1b7baa3269eb329369ebf602110000000ae914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dc6e2f7d8f1fcc7afb568936c437ff4726365d48bc2a71ac2ef0912928a610c1 0.600000000000 1596838 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": 1116389, "vin": [ { "gen": { "height": 1116379 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dc6e2f7d8f1fcc7afb568936c437ff4726365d48bc2a71ac2ef0912928a610c1" } } ], "extra": [ 1, 47, 121, 207, 155, 162, 76, 133, 46, 53, 63, 148, 163, 104, 74, 239, 240, 145, 131, 18, 172, 14, 27, 123, 170, 50, 105, 235, 50, 147, 105, 235, 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