Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: deedbf74abfa70faaba63f3a2053bc454572d98054b02d64ade5f7eb6d5f4692

Tx prefix hash: 8e19d49c98303ac02c2c1655fb420e6da07b756b1a8444704b26269c76635fc2
Tx public key: 57925433fa9317efad092f95fc9a6cdd89a19d6f1ba6b3133a425eaf0f5d1cbf
Timestamp: 1626595092 Timestamp [UCT]: 2021-07-18 07:58:12 Age [y:d:h:m:s]: 03:170:17:02:41
Block: 296108 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 893574 RingCT/type: yes/0
Extra: 0157925433fa9317efad092f95fc9a6cdd89a19d6f1ba6b3133a425eaf0f5d1cbf02110000001604712537000000000000000000

1 output(s) for total of 64.102028351000 dcy

stealth address amount amount idx
00: 43c073d679c2f2726cc6ff9c2dc70cc43b6f44c608503f877b9bfe2ade1b0e1c 64.102028351000 619950 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": 296118, "vin": [ { "gen": { "height": 296108 } } ], "vout": [ { "amount": 64102028351, "target": { "key": "43c073d679c2f2726cc6ff9c2dc70cc43b6f44c608503f877b9bfe2ade1b0e1c" } } ], "extra": [ 1, 87, 146, 84, 51, 250, 147, 23, 239, 173, 9, 47, 149, 252, 154, 108, 221, 137, 161, 157, 111, 27, 166, 179, 19, 58, 66, 94, 175, 15, 93, 28, 191, 2, 17, 0, 0, 0, 22, 4, 113, 37, 55, 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