Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8dd753c44ff254f89c2f1606b7d3bdbcf12b7ce90c32449969d7194dc1b219df

Tx prefix hash: 42f41f63d814c739e1a7569f9c3f13bbecbdfb89886ef4b8e99e327e9c146aad
Tx public key: 49a36c0d48d5d1ae33417a4a0ad50f04f4af5658b75f7c8ff625ff0780e877df
Timestamp: 1735683429 Timestamp [UCT]: 2024-12-31 22:17:09 Age [y:d:h:m:s]: 00:094:01:32:22
Block: 1187444 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 67016 RingCT/type: yes/0
Extra: 0149a36c0d48d5d1ae33417a4a0ad50f04f4af5658b75f7c8ff625ff0780e877df0211000000171f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0b2aef82cccf5b01ca56ae59e8df5c740d97541f73e158842cf7e303a847452f 0.600000000000 1673935 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": 1187454, "vin": [ { "gen": { "height": 1187444 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0b2aef82cccf5b01ca56ae59e8df5c740d97541f73e158842cf7e303a847452f" } } ], "extra": [ 1, 73, 163, 108, 13, 72, 213, 209, 174, 51, 65, 122, 74, 10, 213, 15, 4, 244, 175, 86, 88, 183, 95, 124, 143, 246, 37, 255, 7, 128, 232, 119, 223, 2, 17, 0, 0, 0, 23, 31, 10, 83, 235, 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