Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 04a1ba48469f2aed658c8dae3ac1159f713fde249b9eb74bd4e8702b0cd97ce6

Tx prefix hash: 448f21ef174a638c213a48583d19ad7509e5b1004f33a11ce4617329ae7d77aa
Tx public key: 9a6b3bbc7a1d92f9ee256769a339bdbf0e5cdb7638aece0f35882e54f6927224
Timestamp: 1729270175 Timestamp [UCT]: 2024-10-18 16:49:35 Age [y:d:h:m:s]: 00:189:21:32:45
Block: 1134412 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 135512 RingCT/type: yes/0
Extra: 019a6b3bbc7a1d92f9ee256769a339bdbf0e5cdb7638aece0f35882e54f69272240211000000033cd0fc06000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4ddca52f7647aa8f89bff74ea5428f7c0089dcefbc779b0ba7443d647eecd3ba 0.600000000000 1617713 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": 1134422, "vin": [ { "gen": { "height": 1134412 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4ddca52f7647aa8f89bff74ea5428f7c0089dcefbc779b0ba7443d647eecd3ba" } } ], "extra": [ 1, 154, 107, 59, 188, 122, 29, 146, 249, 238, 37, 103, 105, 163, 57, 189, 191, 14, 92, 219, 118, 56, 174, 206, 15, 53, 136, 46, 84, 246, 146, 114, 36, 2, 17, 0, 0, 0, 3, 60, 208, 252, 6, 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