Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f377c516d9aa5502fb80ffcff0595ff03a098053a5187c433ed2c014c1a50a04

Tx prefix hash: 8352a7c1b6c7c8864f1133f38a0ff65579a98e76a043c4ce2408277f1aeb3ed5
Tx public key: 587308f04da4d5f535b3f2206c82b44b04cf3201053dcd32b2230729fae74642
Timestamp: 1717508679 Timestamp [UCT]: 2024-06-04 13:44:39 Age [y:d:h:m:s]: 01:010:02:58:30
Block: 1036908 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 268049 RingCT/type: yes/0
Extra: 01587308f04da4d5f535b3f2206c82b44b04cf3201053dcd32b2230729fae746420211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e5aeb0f5cc9d53219368f912c7fe009da36c94f56f0fe2908979c94ef151fd78 0.600000000000 1505439 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": 1036918, "vin": [ { "gen": { "height": 1036908 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e5aeb0f5cc9d53219368f912c7fe009da36c94f56f0fe2908979c94ef151fd78" } } ], "extra": [ 1, 88, 115, 8, 240, 77, 164, 213, 245, 53, 179, 242, 32, 108, 130, 180, 75, 4, 207, 50, 1, 5, 61, 205, 50, 178, 35, 7, 41, 250, 231, 70, 66, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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