Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 979db3d33b67a5cb261551dfa892bb77c101d2dab4a00be0bb962498ffc338d7

Tx prefix hash: a5ae49f706859160178b2b7a853c063ccdc602a67c2c39bb20899343061dfc31
Tx public key: 43d9dcda7f64956fff4817735ef8b0e4978dd67c869405c252e19ce068cc44bc
Timestamp: 1682322873 Timestamp [UCT]: 2023-04-24 07:54:33 Age [y:d:h:m:s]: 01:270:18:35:16
Block: 745439 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 454971 RingCT/type: yes/0
Extra: 0143d9dcda7f64956fff4817735ef8b0e4978dd67c869405c252e19ce068cc44bc021100000001b3164c24000000000000000000

1 output(s) for total of 2.079942631000 dcy

stealth address amount amount idx
00: d3ecf1065bbaef87b347924ee7ed8fd58cbad51f2fb9a0ea468612fc5d2a1633 2.079942631000 1192890 of 0

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": 745449, "vin": [ { "gen": { "height": 745439 } } ], "vout": [ { "amount": 2079942631, "target": { "key": "d3ecf1065bbaef87b347924ee7ed8fd58cbad51f2fb9a0ea468612fc5d2a1633" } } ], "extra": [ 1, 67, 217, 220, 218, 127, 100, 149, 111, 255, 72, 23, 115, 94, 248, 176, 228, 151, 141, 214, 124, 134, 148, 5, 194, 82, 225, 156, 224, 104, 204, 68, 188, 2, 17, 0, 0, 0, 1, 179, 22, 76, 36, 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