Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8b6b1abeb4ca4d8b458f0506ac13cc8877495b4a9c297f7a138175d3e4e2b8d2

Tx prefix hash: b8e9ec7fcbaa2885113f64f5e49eb128cf08af7d9b857a3a954c583e3a192ce4
Tx public key: b5b594642ecfd402595b2f0f1567ca6ad97229ab4f5c73cbd7c33231d19db5f0
Timestamp: 1702379833 Timestamp [UCT]: 2023-12-12 11:17:13 Age [y:d:h:m:s]: 01:155:17:30:55
Block: 911493 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 372440 RingCT/type: yes/0
Extra: 01b5b594642ecfd402595b2f0f1567ca6ad97229ab4f5c73cbd7c33231d19db5f002110000000475e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c4d4122541b0e66501b68e8e1d04a7a9473f80819a56e38d0e5adff0099ca083 0.600000000000 1368697 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": 911503, "vin": [ { "gen": { "height": 911493 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c4d4122541b0e66501b68e8e1d04a7a9473f80819a56e38d0e5adff0099ca083" } } ], "extra": [ 1, 181, 181, 148, 100, 46, 207, 212, 2, 89, 91, 47, 15, 21, 103, 202, 106, 217, 114, 41, 171, 79, 92, 115, 203, 215, 195, 50, 49, 209, 157, 181, 240, 2, 17, 0, 0, 0, 4, 117, 227, 240, 233, 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