Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c15d8c2e92111792832e2f19495cd5517e4468279f7deff9f5b7426fb4b2589f

Tx prefix hash: 3d74c0d050cf211974a47c0b56c0940f96081b1532224a0e5e655807e6c47b2f
Tx public key: faeb28d5b0da6f0570ac2a05c68e7a501e1476f76ebff4696c5c5f102b596fac
Timestamp: 1725003316 Timestamp [UCT]: 2024-08-30 07:35:16 Age [y:d:h:m:s]: 01:071:02:56:26
Block: 1099034 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 309270 RingCT/type: yes/0
Extra: 01faeb28d5b0da6f0570ac2a05c68e7a501e1476f76ebff4696c5c5f102b596fac021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6be5174e534ca7250f4857f3499175dca25e9f22374be0d48b4d38cd39513556 0.600000000000 1574953 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": 1099044, "vin": [ { "gen": { "height": 1099034 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6be5174e534ca7250f4857f3499175dca25e9f22374be0d48b4d38cd39513556" } } ], "extra": [ 1, 250, 235, 40, 213, 176, 218, 111, 5, 112, 172, 42, 5, 198, 142, 122, 80, 30, 20, 118, 247, 110, 191, 244, 105, 108, 92, 95, 16, 43, 89, 111, 172, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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