Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ebe427e2ad2e01b938523c9bb3759054bacbf8515a2a3c99171e3c8b343a62a8

Tx prefix hash: 7147c37f789f2e0b7d327ad9c749b6b044e0595c415c54fbd885612de4695a07
Tx public key: 79bcb9d99df110d1b17ac4e0900a1e941d1a4eebe9788c46711d87826cb90438
Timestamp: 1718645798 Timestamp [UCT]: 2024-06-17 17:36:38 Age [y:d:h:m:s]: 01:207:00:31:43
Block: 1046329 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 406614 RingCT/type: yes/0
Extra: 0179bcb9d99df110d1b17ac4e0900a1e941d1a4eebe9788c46711d87826cb9043802110000000852d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a55c78094e471e2b8425063fcb1fb1ecde8275c437404a39302cccb8623c8299 0.600000000000 1516140 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": 1046339, "vin": [ { "gen": { "height": 1046329 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a55c78094e471e2b8425063fcb1fb1ecde8275c437404a39302cccb8623c8299" } } ], "extra": [ 1, 121, 188, 185, 217, 157, 241, 16, 209, 177, 122, 196, 224, 144, 10, 30, 148, 29, 26, 78, 235, 233, 120, 140, 70, 113, 29, 135, 130, 108, 185, 4, 56, 2, 17, 0, 0, 0, 8, 82, 212, 126, 148, 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