Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5a52c22c37f4fefebc9685ae37c4b5de1ab0c6f09fc83855a80ee683088cb47e

Tx prefix hash: c2fa95dc11038ebdc717a77c92fcf04c32608c45ec833af7c05a4b48a9df53f5
Tx public key: dcd43e171acdcf092a131337b1df3fe5060ef584e405ff93fb1fe3993d859f16
Timestamp: 1722477288 Timestamp [UCT]: 2024-08-01 01:54:48 Age [y:d:h:m:s]: 00:260:22:30:10
Block: 1078092 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 186406 RingCT/type: yes/0
Extra: 01dcd43e171acdcf092a131337b1df3fe5060ef584e405ff93fb1fe3993d859f1602110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 449218df22777b8c692c5bd5c4f155c2910f9044f248cdca6ec40e217a6e4e43 0.600000000000 1550655 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": 1078102, "vin": [ { "gen": { "height": 1078092 } } ], "vout": [ { "amount": 600000000, "target": { "key": "449218df22777b8c692c5bd5c4f155c2910f9044f248cdca6ec40e217a6e4e43" } } ], "extra": [ 1, 220, 212, 62, 23, 26, 205, 207, 9, 42, 19, 19, 55, 177, 223, 63, 229, 6, 14, 245, 132, 228, 5, 255, 147, 251, 31, 227, 153, 61, 133, 159, 22, 2, 17, 0, 0, 0, 4, 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