Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 96c272a2fb43560559a5746bd3de36f9d32b4dd0050f6e056b987d40f1f62a8e

Tx prefix hash: 0a03c8aff3c59e3eeeb9edccb6896f062dd7f566666b207584efc0979bba1474
Tx public key: ddb8f6187b1f5c69517c1c2b34468dbaef20b1e6aff82b17c0c4c12848b34056
Timestamp: 1698460263 Timestamp [UCT]: 2023-10-28 02:31:03 Age [y:d:h:m:s]: 01:233:08:14:32
Block: 879203 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 427690 RingCT/type: yes/0
Extra: 01ddb8f6187b1f5c69517c1c2b34468dbaef20b1e6aff82b17c0c4c12848b3405602110000000633af99f4000000000000000000

1 output(s) for total of 0.749610222000 dcy

stealth address amount amount idx
00: 8666bc98e018b41ee9404347ed3dbe4688e044d23dc24506bc0e669962a139c3 0.749610222000 1334707 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": 879213, "vin": [ { "gen": { "height": 879203 } } ], "vout": [ { "amount": 749610222, "target": { "key": "8666bc98e018b41ee9404347ed3dbe4688e044d23dc24506bc0e669962a139c3" } } ], "extra": [ 1, 221, 184, 246, 24, 123, 31, 92, 105, 81, 124, 28, 43, 52, 70, 141, 186, 239, 32, 177, 230, 175, 248, 43, 23, 192, 196, 193, 40, 72, 179, 64, 86, 2, 17, 0, 0, 0, 6, 51, 175, 153, 244, 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