Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 76acdf8610d370d4707ed4f281be1b0383aad0fa87f5361db5681be21421440d

Tx prefix hash: b41615e9116129492136c28cfd9cf808231b55f7e33b642212784da43d7835a6
Tx public key: c19b1bdbfe079b55b3ae621fabca5c3d78dd8a921646694df06ae9118df8a122
Timestamp: 1722395158 Timestamp [UCT]: 2024-07-31 03:05:58 Age [y:d:h:m:s]: 00:253:15:09:32
Block: 1077400 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 181185 RingCT/type: yes/0
Extra: 01c19b1bdbfe079b55b3ae621fabca5c3d78dd8a921646694df06ae9118df8a12202110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2969a1a1fcb86c74e055a72658162b9393d866c41c4e8ed16b7adc6a4ee23e5b 0.600000000000 1549947 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": 1077410, "vin": [ { "gen": { "height": 1077400 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2969a1a1fcb86c74e055a72658162b9393d866c41c4e8ed16b7adc6a4ee23e5b" } } ], "extra": [ 1, 193, 155, 27, 219, 254, 7, 155, 85, 179, 174, 98, 31, 171, 202, 92, 61, 120, 221, 138, 146, 22, 70, 105, 77, 240, 106, 233, 17, 141, 248, 161, 34, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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