Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ba5ddef1c9f0dc1bd4b99e84711946009c41fe6e40ea01400ea52ab67c3ffd3a

Tx prefix hash: 9173dca6443b8a0224cc50d9e3369cb78f12b1621340186e571029fb7241f67a
Tx public key: 44d213d2e886c1ded8ecdca3311fb5b46d6c320a595956beb69a919cc620231a
Timestamp: 1675519576 Timestamp [UCT]: 2023-02-04 14:06:16 Age [y:d:h:m:s]: 02:108:04:25:35
Block: 689678 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 598977 RingCT/type: yes/0
Extra: 0144d213d2e886c1ded8ecdca3311fb5b46d6c320a595956beb69a919cc620231a0211000000015029cbac000000000000000000

1 output(s) for total of 3.182807813000 dcy

stealth address amount amount idx
00: ea1a647d427217ef52117e530de24d517629c28517dffb40343b71f1f6a4c3a0 3.182807813000 1132370 of 0

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": 689688, "vin": [ { "gen": { "height": 689678 } } ], "vout": [ { "amount": 3182807813, "target": { "key": "ea1a647d427217ef52117e530de24d517629c28517dffb40343b71f1f6a4c3a0" } } ], "extra": [ 1, 68, 210, 19, 210, 232, 134, 193, 222, 216, 236, 220, 163, 49, 31, 181, 180, 109, 108, 50, 10, 89, 89, 86, 190, 182, 154, 145, 156, 198, 32, 35, 26, 2, 17, 0, 0, 0, 1, 80, 41, 203, 172, 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