Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e2c25183319a3ae61739c18b64c619acba7fd27417e322c2e6537cad3842b04f

Tx prefix hash: 09b0d2de35c50ca725b67d0036dbd1afce0bb994aff6de9a543c1a4939d316c9
Tx public key: 54e6e59884edb111ae6553c564d9213990e9a904a73a55fb2cf9af941ebc572d
Timestamp: 1738504564 Timestamp [UCT]: 2025-02-02 13:56:04 Age [y:d:h:m:s]: 00:292:03:01:37
Block: 1210532 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 206547 RingCT/type: yes/0
Extra: 0154e6e59884edb111ae6553c564d9213990e9a904a73a55fb2cf9af941ebc572d0211000000071f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 93d3f2970718ca46fbcf3034a05cc48f0ffb8e8b5838ef711bc34b93b2d22a75 0.600000000000 1697285 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": 1210542, "vin": [ { "gen": { "height": 1210532 } } ], "vout": [ { "amount": 600000000, "target": { "key": "93d3f2970718ca46fbcf3034a05cc48f0ffb8e8b5838ef711bc34b93b2d22a75" } } ], "extra": [ 1, 84, 230, 229, 152, 132, 237, 177, 17, 174, 101, 83, 197, 100, 217, 33, 57, 144, 233, 169, 4, 167, 58, 85, 251, 44, 249, 175, 148, 30, 188, 87, 45, 2, 17, 0, 0, 0, 7, 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