Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f9ecc6b5749850c56e1b5ea8a42635a7b68dddfcbbf0a2500c56a7fffe41a8f3

Tx prefix hash: 5d184bfbb872813d332e035d446bf745b540e2d74735ca66a989b69e689aaf66
Tx public key: 1ed30eae1bfb28a36ef2e2c79e9af0b1f52860930f8b81bebc11d6008611ff67
Timestamp: 1732344906 Timestamp [UCT]: 2024-11-23 06:55:06 Age [y:d:h:m:s]: 00:000:14:46:22
Block: 1159804 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 434 RingCT/type: yes/0
Extra: 011ed30eae1bfb28a36ef2e2c79e9af0b1f52860930f8b81bebc11d6008611ff67021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: deabf6b968eae13fc672f067b97f12f02d68ddc1e25a84ea4165e74e2d491500 0.600000000000 1645443 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": 1159814, "vin": [ { "gen": { "height": 1159804 } } ], "vout": [ { "amount": 600000000, "target": { "key": "deabf6b968eae13fc672f067b97f12f02d68ddc1e25a84ea4165e74e2d491500" } } ], "extra": [ 1, 30, 211, 14, 174, 27, 251, 40, 163, 110, 242, 226, 199, 158, 154, 240, 177, 245, 40, 96, 147, 15, 139, 129, 190, 188, 17, 214, 0, 134, 17, 255, 103, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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