Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f97eb790988b2c1f309e866b837daddd4d6c948c7f8460335af0e4d4c40e0aed

Tx prefix hash: abb384ba8f43ebe028fbe726fedce54b4dbb2aed6e761664768348e8e52404c6
Tx public key: ae5cdee1ba089406ab30f0e41c07bfa6c124dc3887891b16e5d0bb29b050920b
Timestamp: 1704136085 Timestamp [UCT]: 2024-01-01 19:08:05 Age [y:d:h:m:s]: 01:313:17:43:08
Block: 926031 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 483059 RingCT/type: yes/0
Extra: 01ae5cdee1ba089406ab30f0e41c07bfa6c124dc3887891b16e5d0bb29b050920b0211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7dd3ac2f5c6341511f2e3053e1069b2fecaeb28d3be05947cd6e24158fe47834 0.600000000000 1383801 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": 926041, "vin": [ { "gen": { "height": 926031 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7dd3ac2f5c6341511f2e3053e1069b2fecaeb28d3be05947cd6e24158fe47834" } } ], "extra": [ 1, 174, 92, 222, 225, 186, 8, 148, 6, 171, 48, 240, 228, 28, 7, 191, 166, 193, 36, 220, 56, 135, 137, 27, 22, 229, 208, 187, 41, 176, 80, 146, 11, 2, 17, 0, 0, 0, 4, 0, 17, 5, 91, 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