Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6ff13c896933a2db863d3c8f46d4e156ddaa76e250bff1b3c649f15d7154dbb1

Tx prefix hash: 718461101d99c1ac1425560865c00a2955c28840ed48684205b94c568815c52b
Tx public key: 90d1fa57113d9e2479b0db3378ead82489e14c009b5cf0a4a98614c56bae440a
Timestamp: 1632095099 Timestamp [UCT]: 2021-09-19 23:44:59 Age [y:d:h:m:s]: 03:109:02:47:53
Block: 337170 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 853988 RingCT/type: yes/0
Extra: 0190d1fa57113d9e2479b0db3378ead82489e14c009b5cf0a4a98614c56bae440a021100000010a272b9cb000000000000000000

1 output(s) for total of 46.862318034000 dcy

stealth address amount amount idx
00: 8d0f25821d90c2bbd2312cb30dca9b1df5298cbc9e237a53ad864ecb39e573ac 46.862318034000 694387 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": 337180, "vin": [ { "gen": { "height": 337170 } } ], "vout": [ { "amount": 46862318034, "target": { "key": "8d0f25821d90c2bbd2312cb30dca9b1df5298cbc9e237a53ad864ecb39e573ac" } } ], "extra": [ 1, 144, 209, 250, 87, 17, 61, 158, 36, 121, 176, 219, 51, 120, 234, 216, 36, 137, 225, 76, 0, 155, 92, 240, 164, 169, 134, 20, 197, 107, 174, 68, 10, 2, 17, 0, 0, 0, 16, 162, 114, 185, 203, 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