Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 030c64402f8b22b043c220ab870c3872caff950866f3902e37697c56ad8f806a

Tx prefix hash: 16bef370e3f3c2178a447abc628097813e9aa5a6b5558323f750ee0aeb727ed2
Tx public key: b00f295d236ddc786fb9b139675683cb7ef003295d2acc5b546d95762ce9d4f1
Timestamp: 1728644456 Timestamp [UCT]: 2024-10-11 11:00:56 Age [y:d:h:m:s]: 00:132:01:01:11
Block: 1129225 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 94114 RingCT/type: yes/0
Extra: 01b00f295d236ddc786fb9b139675683cb7ef003295d2acc5b546d95762ce9d4f102110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2b8917b6a2b4e1466b29255693cfa8603e67a53107fdd4b9c4a3e88d5b3b9ab4 0.600000000000 1612050 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": 1129235, "vin": [ { "gen": { "height": 1129225 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2b8917b6a2b4e1466b29255693cfa8603e67a53107fdd4b9c4a3e88d5b3b9ab4" } } ], "extra": [ 1, 176, 15, 41, 93, 35, 109, 220, 120, 111, 185, 177, 57, 103, 86, 131, 203, 126, 240, 3, 41, 93, 42, 204, 91, 84, 109, 149, 118, 44, 233, 212, 241, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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