Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3743271be2806e8653c34a11426b7fccd7af0c18cc0e69f2525c91dea7f3dc6f

Tx prefix hash: 59fc733c15826f31977e14e247ae9fa08ba58e8751049054dbe710c3cc43b224
Tx public key: 020f6219b7bdeb91ed477869cd3036c44a13e633869b6327f5a1709df884f499
Timestamp: 1701928676 Timestamp [UCT]: 2023-12-07 05:57:56 Age [y:d:h:m:s]: 01:362:06:59:05
Block: 907735 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 517844 RingCT/type: yes/0
Extra: 01020f6219b7bdeb91ed477869cd3036c44a13e633869b6327f5a1709df884f49902110000000275e3f0e9000000000000000000

1 output(s) for total of 0.602971935000 dcy

stealth address amount amount idx
00: 180717e49919d69c9cd0b3bf46c7b7cfcd9c1bec489bea6128c6c318bd95d056 0.602971935000 1364728 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": 907745, "vin": [ { "gen": { "height": 907735 } } ], "vout": [ { "amount": 602971935, "target": { "key": "180717e49919d69c9cd0b3bf46c7b7cfcd9c1bec489bea6128c6c318bd95d056" } } ], "extra": [ 1, 2, 15, 98, 25, 183, 189, 235, 145, 237, 71, 120, 105, 205, 48, 54, 196, 74, 19, 230, 51, 134, 155, 99, 39, 245, 161, 112, 157, 248, 132, 244, 153, 2, 17, 0, 0, 0, 2, 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