Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 167c8c83eb889efc0c118ba5912c0b955617d4ec11702c2e5efc9ed4299279c7

Tx prefix hash: 8f8450ff5a3a674e84b02ca99b1c2807d0fdc1bf45196dcfa58b4c8f5d32331e
Tx public key: 3c4d5b822f4179e8b921c3585e27544b172fa92fbddb783708a6a262a1e0b648
Timestamp: 1580616292 Timestamp [UCT]: 2020-02-02 04:04:52 Age [y:d:h:m:s]: 05:276:12:18:25
Block: 56838 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1347335 RingCT/type: yes/0
Extra: 013c4d5b822f4179e8b921c3585e27544b172fa92fbddb783708a6a262a1e0b64802110000000149b77a3d000000000000000000

1 output(s) for total of 397.807470341000 dcy

stealth address amount amount idx
00: 9edeb17ae5d1b14abd172a26cb11506c951f1da8de533613db855e0b9ee129f5 397.807470341000 104815 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": 56848, "vin": [ { "gen": { "height": 56838 } } ], "vout": [ { "amount": 397807470341, "target": { "key": "9edeb17ae5d1b14abd172a26cb11506c951f1da8de533613db855e0b9ee129f5" } } ], "extra": [ 1, 60, 77, 91, 130, 47, 65, 121, 232, 185, 33, 195, 88, 94, 39, 84, 75, 23, 47, 169, 47, 189, 219, 120, 55, 8, 166, 162, 98, 161, 224, 182, 72, 2, 17, 0, 0, 0, 1, 73, 183, 122, 61, 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