Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d7f68d368d537f53fb120d440cbc1b71c2fc6b2980c6014c2bc94a07cf8a0e13

Tx prefix hash: 3eab1dfda14931635e57df2e440c9956bb439538994e8459f86c6cf334989d3d
Tx public key: e50c5b0e78a86bc2720840cc4aec4434f983b472d2a2975713caad0f3ab3015f
Timestamp: 1696228333 Timestamp [UCT]: 2023-10-02 06:32:13 Age [y:d:h:m:s]: 02:062:16:09:37
Block: 860678 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 564463 RingCT/type: yes/0
Extra: 01e50c5b0e78a86bc2720840cc4aec4434f983b472d2a2975713caad0f3ab3015f021100000001faf35c9c000000000000000000

1 output(s) for total of 0.863408943000 dcy

stealth address amount amount idx
00: 604138a613142c7758d1dc867e2e6c59e70d5f07747e0b77de383be18e1bab68 0.863408943000 1314974 of 0

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": 860688, "vin": [ { "gen": { "height": 860678 } } ], "vout": [ { "amount": 863408943, "target": { "key": "604138a613142c7758d1dc867e2e6c59e70d5f07747e0b77de383be18e1bab68" } } ], "extra": [ 1, 229, 12, 91, 14, 120, 168, 107, 194, 114, 8, 64, 204, 74, 236, 68, 52, 249, 131, 180, 114, 210, 162, 151, 87, 19, 202, 173, 15, 58, 179, 1, 95, 2, 17, 0, 0, 0, 1, 250, 243, 92, 156, 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