Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1b8752f2b02eac522be762db74970528242da6794a730b7a3f756bce6f2dba57

Tx prefix hash: b4e1cad7ca60e46f7db0a9d0590d595897017aa3b6344548d0b310f048faf803
Tx public key: 77be6b1b0de5afacebab204b2f7136b2b41a0f5b374e67c3443060dea1b0946c
Timestamp: 1699398359 Timestamp [UCT]: 2023-11-07 23:05:59 Age [y:d:h:m:s]: 01:161:12:32:47
Block: 886766 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 376629 RingCT/type: yes/0
Extra: 0177be6b1b0de5afacebab204b2f7136b2b41a0f5b374e67c3443060dea1b0946c02110000000475e3f0e9000000000000000000

1 output(s) for total of 0.707580948000 dcy

stealth address amount amount idx
00: 329166e170d693106d223020017ac253accc0800dbe78bcee260744d774469e7 0.707580948000 1342609 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": 886776, "vin": [ { "gen": { "height": 886766 } } ], "vout": [ { "amount": 707580948, "target": { "key": "329166e170d693106d223020017ac253accc0800dbe78bcee260744d774469e7" } } ], "extra": [ 1, 119, 190, 107, 27, 13, 229, 175, 172, 235, 171, 32, 75, 47, 113, 54, 178, 180, 26, 15, 91, 55, 78, 103, 195, 68, 48, 96, 222, 161, 176, 148, 108, 2, 17, 0, 0, 0, 4, 117, 227, 240, 233, 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