Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a479abece49410148153c025ce9413f6aeb65486e0a1b3a0b70c8af815e30d29

Tx prefix hash: 284d64a905ffadb2dffcef0585437ac3bdb85fa7e666377da42d6f4afb635357
Tx public key: a0f020f89d4752d5c11b340ebfd4bb2c86cba67e74b76059b65473ae4057fbd5
Timestamp: 1714976625 Timestamp [UCT]: 2024-05-06 06:23:45 Age [y:d:h:m:s]: 00:357:23:04:58
Block: 1015908 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 255900 RingCT/type: yes/0
Extra: 01a0f020f89d4752d5c11b340ebfd4bb2c86cba67e74b76059b65473ae4057fbd50211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9c259fa279851d71deafb7a63a4a6ea48434ed0b6f97844d4f6109a18c8c98c4 0.600000000000 1479351 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": 1015918, "vin": [ { "gen": { "height": 1015908 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9c259fa279851d71deafb7a63a4a6ea48434ed0b6f97844d4f6109a18c8c98c4" } } ], "extra": [ 1, 160, 240, 32, 248, 157, 71, 82, 213, 193, 27, 52, 14, 191, 212, 187, 44, 134, 203, 166, 126, 116, 183, 96, 89, 182, 84, 115, 174, 64, 87, 251, 213, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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