Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 34a777bb45f78448bf74eda21629302cdd8f0f008c26e611c9da569feb555232

Tx prefix hash: 7068ae4bd0d310c52d835414a185a74a782aee68650440e1249ae05074cfc9b9
Tx public key: bbf2b70df3c8c52592212a21402fab37d8578f577422f1597970a1f7ebcc43ea
Timestamp: 1699508424 Timestamp [UCT]: 2023-11-09 05:40:24 Age [y:d:h:m:s]: 01:143:15:30:29
Block: 887674 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 363844 RingCT/type: yes/0
Extra: 01bbf2b70df3c8c52592212a21402fab37d8578f577422f1597970a1f7ebcc43ea02110000000233af99f4000000000000000000

1 output(s) for total of 0.702696108000 dcy

stealth address amount amount idx
00: 6de535bea3514bf001d6184b1a2c9942f9c230ac8345a2c1e912fb2f03b706a2 0.702696108000 1343567 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": 887684, "vin": [ { "gen": { "height": 887674 } } ], "vout": [ { "amount": 702696108, "target": { "key": "6de535bea3514bf001d6184b1a2c9942f9c230ac8345a2c1e912fb2f03b706a2" } } ], "extra": [ 1, 187, 242, 183, 13, 243, 200, 197, 37, 146, 33, 42, 33, 64, 47, 171, 55, 216, 87, 143, 87, 116, 34, 241, 89, 121, 112, 161, 247, 235, 204, 67, 234, 2, 17, 0, 0, 0, 2, 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