Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a23ddeaf855d590e3d71d60086b9f6b07d03ba58db2b63b06b24aa97fd19f657

Tx prefix hash: b8d0e29814ad432b354c81fb1cfd40efc9560e6123c651229ebd0e6086fc6b9d
Tx public key: 6abb284f14cd659d8fa4face617eaa47bfc7ebbc2205aa3edf1f7c652c369b1a
Timestamp: 1710840682 Timestamp [UCT]: 2024-03-19 09:31:22 Age [y:d:h:m:s]: 01:235:23:32:12
Block: 981638 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 427340 RingCT/type: yes/0
Extra: 016abb284f14cd659d8fa4face617eaa47bfc7ebbc2205aa3edf1f7c652c369b1a021100000001a5df9d86000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 80b7334355c55c345792e93018d461f26859ee5c2c82cb8161f6e6739ec256c0 0.600000000000 1441735 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": 981648, "vin": [ { "gen": { "height": 981638 } } ], "vout": [ { "amount": 600000000, "target": { "key": "80b7334355c55c345792e93018d461f26859ee5c2c82cb8161f6e6739ec256c0" } } ], "extra": [ 1, 106, 187, 40, 79, 20, 205, 101, 157, 143, 164, 250, 206, 97, 126, 170, 71, 191, 199, 235, 188, 34, 5, 170, 62, 223, 31, 124, 101, 44, 54, 155, 26, 2, 17, 0, 0, 0, 1, 165, 223, 157, 134, 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