Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ca124b07c3e3bd986c3f460d71dec3ed2d1f43c1ed8204974c21864613aa2bc4

Tx prefix hash: 0373f6a29b4d735a8c7cfc1f7197e9990d2ecae6a55b75dfd8266946ff176ef5
Tx public key: 74d263bf6269ffb9166fc2c7625b9babb009879dcdd6b31c5d9b0c4034ca5496
Timestamp: 1709037677 Timestamp [UCT]: 2024-02-27 12:41:17 Age [y:d:h:m:s]: 00:275:06:51:20
Block: 966680 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 197082 RingCT/type: yes/0
Extra: 0174d263bf6269ffb9166fc2c7625b9babb009879dcdd6b31c5d9b0c4034ca54960211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 54bb0d9d4bb5b0da47c80ff434a3cc2b44a1afec3b2d01fcd2e3edec6fdbff22 0.600000000000 1426447 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": 966690, "vin": [ { "gen": { "height": 966680 } } ], "vout": [ { "amount": 600000000, "target": { "key": "54bb0d9d4bb5b0da47c80ff434a3cc2b44a1afec3b2d01fcd2e3edec6fdbff22" } } ], "extra": [ 1, 116, 210, 99, 191, 98, 105, 255, 185, 22, 111, 194, 199, 98, 91, 155, 171, 176, 9, 135, 157, 205, 214, 179, 28, 93, 155, 12, 64, 52, 202, 84, 150, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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