Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 334f058c274e906b9bf0c93c91c8218fc5fc24fd7381fc1f83bb523b3961e182

Tx prefix hash: e4c0d77421bc9879742d556959cf636133e1dd7def4f8808e30968a3e171f62c
Tx public key: d6d4536dd426d8b7600ac6b2d9dcf452d879a6e2b407ad001aa631b52e450307
Timestamp: 1731181514 Timestamp [UCT]: 2024-11-09 19:45:14 Age [y:d:h:m:s]: 00:186:05:48:36
Block: 1150170 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 132959 RingCT/type: yes/0
Extra: 01d6d4536dd426d8b7600ac6b2d9dcf452d879a6e2b407ad001aa631b52e450307021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4e2f972d57cac497a72787d988954f86e48ebb95e75ff6638d280112b880ad7d 0.600000000000 1635399 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": 1150180, "vin": [ { "gen": { "height": 1150170 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4e2f972d57cac497a72787d988954f86e48ebb95e75ff6638d280112b880ad7d" } } ], "extra": [ 1, 214, 212, 83, 109, 212, 38, 216, 183, 96, 10, 198, 178, 217, 220, 244, 82, 216, 121, 166, 226, 180, 7, 173, 0, 26, 166, 49, 181, 46, 69, 3, 7, 2, 17, 0, 0, 0, 1, 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