Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6786355155447fa9aa495f4c89f6dd0ea75150f5134848d05264b6426b3fdc9b

Tx prefix hash: a0109d40520232c39dbb9c8b2a60329b67ce0d4eafacfe6e3be0a07160c93e38
Tx public key: 2e99d1b38d45a8fd879a49b054117304ed01f515d5a73975a09b79a2a0016a72
Timestamp: 1728298966 Timestamp [UCT]: 2024-10-07 11:02:46 Age [y:d:h:m:s]: 00:108:21:42:02
Block: 1126358 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 77811 RingCT/type: yes/0
Extra: 012e99d1b38d45a8fd879a49b054117304ed01f515d5a73975a09b79a2a0016a7202110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6c3561d7e9990e8ccda5522e64ebaa8a86316d6939aa7133676ed6655e389c33 0.600000000000 1609149 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": 1126368, "vin": [ { "gen": { "height": 1126358 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6c3561d7e9990e8ccda5522e64ebaa8a86316d6939aa7133676ed6655e389c33" } } ], "extra": [ 1, 46, 153, 209, 179, 141, 69, 168, 253, 135, 154, 73, 176, 84, 17, 115, 4, 237, 1, 245, 21, 213, 167, 57, 117, 160, 155, 121, 162, 160, 1, 106, 114, 2, 17, 0, 0, 0, 3, 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