Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 284a2eefa653e8c78d2f50e4458515f44fac002299b245951bd8bf127129531d

Tx prefix hash: 3f8463e0a3d54d6f2f536e07c4d6a5adaa46bdff38b23601cd329380bcd4f8dc
Tx public key: 91764e0bb627ff369f07c54465e15dfd78dcec5b206f0b1c0216a3c434447a6f
Timestamp: 1694774424 Timestamp [UCT]: 2023-09-15 10:40:24 Age [y:d:h:m:s]: 01:198:08:29:23
Block: 848607 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 402856 RingCT/type: yes/0
Extra: 0191764e0bb627ff369f07c54465e15dfd78dcec5b206f0b1c0216a3c434447a6f021100000003e6d27f9c000000000000000000

1 output(s) for total of 0.946700909000 dcy

stealth address amount amount idx
00: f2e6133e7191ba093a1840f1e9cde16d10e15aa6ab87bc3b732f3fb6e9cf5818 0.946700909000 1302223 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": 848617, "vin": [ { "gen": { "height": 848607 } } ], "vout": [ { "amount": 946700909, "target": { "key": "f2e6133e7191ba093a1840f1e9cde16d10e15aa6ab87bc3b732f3fb6e9cf5818" } } ], "extra": [ 1, 145, 118, 78, 11, 182, 39, 255, 54, 159, 7, 197, 68, 101, 225, 93, 253, 120, 220, 236, 91, 32, 111, 11, 28, 2, 22, 163, 196, 52, 68, 122, 111, 2, 17, 0, 0, 0, 3, 230, 210, 127, 156, 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