Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a31cec477c4c57ce9a13c0bb96436c7122f3c36f6d9923eb1b8a9fd7a310c18e

Tx prefix hash: 0a11d2a69499f18b0170828278bec863e3517286c71694f176f01f7270749f8d
Tx public key: e88904eee992309c1e6368116f788df9d6d173359b95f6e3837483b43dc94726
Timestamp: 1735627745 Timestamp [UCT]: 2024-12-31 06:49:05 Age [y:d:h:m:s]: 00:096:23:01:32
Block: 1186988 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 69071 RingCT/type: yes/0
Extra: 01e88904eee992309c1e6368116f788df9d6d173359b95f6e3837483b43dc94726021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 97a54e6d98cf715f5b8c1a368cc5e6d1fa01bb8befd3bbb9e026532a50f969d2 0.600000000000 1673475 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": 1186998, "vin": [ { "gen": { "height": 1186988 } } ], "vout": [ { "amount": 600000000, "target": { "key": "97a54e6d98cf715f5b8c1a368cc5e6d1fa01bb8befd3bbb9e026532a50f969d2" } } ], "extra": [ 1, 232, 137, 4, 238, 233, 146, 48, 156, 30, 99, 104, 17, 111, 120, 141, 249, 214, 209, 115, 53, 155, 149, 246, 227, 131, 116, 131, 180, 61, 201, 71, 38, 2, 17, 0, 0, 0, 3, 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