Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: db892d95b6009b72f0d26ced4a327525ea7211e49af76a520bb721e52ada7c70

Tx prefix hash: c7704263ff0ecdf9a7755950c5adb4cca0625120d3a0d56dda18c4d528df133e
Tx public key: 218dcb87bfe8c6c84269dc36fb808fdaa0ab0dc42a01e5a691351a1d6097d637
Timestamp: 1716931320 Timestamp [UCT]: 2024-05-28 21:22:00 Age [y:d:h:m:s]: 00:300:11:13:53
Block: 1032132 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 214720 RingCT/type: yes/0
Extra: 01218dcb87bfe8c6c84269dc36fb808fdaa0ab0dc42a01e5a691351a1d6097d637021100000003c5452960000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b60fb304523d11610f15c91172d1d54c48016f0339e278c026cc0964f8fc3cf2 0.600000000000 1500581 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": 1032142, "vin": [ { "gen": { "height": 1032132 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b60fb304523d11610f15c91172d1d54c48016f0339e278c026cc0964f8fc3cf2" } } ], "extra": [ 1, 33, 141, 203, 135, 191, 232, 198, 200, 66, 105, 220, 54, 251, 128, 143, 218, 160, 171, 13, 196, 42, 1, 229, 166, 145, 53, 26, 29, 96, 151, 214, 55, 2, 17, 0, 0, 0, 3, 197, 69, 41, 96, 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