Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d7548355b9fad1700a3ee8c9c951f3d66d18c6f1d762cc0acac7a50f44297ee3

Tx prefix hash: e6706612e1ff4ddfc725250f617ebf0b394a5fc70c9b61aa03f57fdb7a089e76
Tx public key: 797f3b5dbefbafa4996ab1d7eb920b02a6a063d407a2708815f5cea40655238f
Timestamp: 1706156400 Timestamp [UCT]: 2024-01-25 04:20:00 Age [y:d:h:m:s]: 01:133:02:37:01
Block: 942755 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 356278 RingCT/type: yes/0
Extra: 01797f3b5dbefbafa4996ab1d7eb920b02a6a063d407a2708815f5cea40655238f02110000000752d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8bbf6d61b9354bd1d39bbc3196633ccf40a97775f2770f40dcb6076e9200040d 0.600000000000 1400933 of 15

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": 942765, "vin": [ { "gen": { "height": 942755 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8bbf6d61b9354bd1d39bbc3196633ccf40a97775f2770f40dcb6076e9200040d" } } ], "extra": [ 1, 121, 127, 59, 93, 190, 251, 175, 164, 153, 106, 177, 215, 235, 146, 11, 2, 166, 160, 99, 212, 7, 162, 112, 136, 21, 245, 206, 164, 6, 85, 35, 143, 2, 17, 0, 0, 0, 7, 82, 212, 126, 148, 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