Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2601f076f9c0c0bf511ce880162043007a131c890974bfcf1637774a2a59e8f4

Tx prefix hash: d6bb4a67949c3a2b1cedfd2c27e379a55ee1ec9cb0c0984bd3ae6176d53cded4
Tx public key: 1730ac769f57fb713d1c2046d73da125870285e12e8c45161f2532728562f8df
Timestamp: 1721753292 Timestamp [UCT]: 2024-07-23 16:48:12 Age [y:d:h:m:s]: 00:329:08:15:27
Block: 1072084 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 235227 RingCT/type: yes/0
Extra: 011730ac769f57fb713d1c2046d73da125870285e12e8c45161f2532728562f8df021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 208aa38a7981c6ebfedc32dda98f194d8bbb534a2e236adb852dee988a0bf1b0 0.600000000000 1544531 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": 1072094, "vin": [ { "gen": { "height": 1072084 } } ], "vout": [ { "amount": 600000000, "target": { "key": "208aa38a7981c6ebfedc32dda98f194d8bbb534a2e236adb852dee988a0bf1b0" } } ], "extra": [ 1, 23, 48, 172, 118, 159, 87, 251, 113, 61, 28, 32, 70, 215, 61, 161, 37, 135, 2, 133, 225, 46, 140, 69, 22, 31, 37, 50, 114, 133, 98, 248, 223, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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