Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7f95f899ae2821df7ddf1b45d71211b346b08162c2dc2e07c6f38377e41785bf

Tx prefix hash: 492af6f9735b04525ea59bb3d30c0678a5bc12789cbda1f0e61c4c8507851e54
Tx public key: eff1aba463fdeddc65c0afd7e71ec113a905f58a793191d2c4128403019b9aae
Timestamp: 1663537212 Timestamp [UCT]: 2022-09-18 21:40:12 Age [y:d:h:m:s]: 02:041:00:36:11
Block: 590830 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 550834 RingCT/type: yes/0
Extra: 01eff1aba463fdeddc65c0afd7e71ec113a905f58a793191d2c4128403019b9aae02110000000475e3f0e9000000000000000000

1 output(s) for total of 6.766047121000 dcy

stealth address amount amount idx
00: fca3a92a07bbdb0cb84e74d065e0d4df624f1db7489f3fbdf0b80aabbeaefa6e 6.766047121000 1025295 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": 590840, "vin": [ { "gen": { "height": 590830 } } ], "vout": [ { "amount": 6766047121, "target": { "key": "fca3a92a07bbdb0cb84e74d065e0d4df624f1db7489f3fbdf0b80aabbeaefa6e" } } ], "extra": [ 1, 239, 241, 171, 164, 99, 253, 237, 220, 101, 192, 175, 215, 231, 30, 193, 19, 169, 5, 245, 138, 121, 49, 145, 210, 196, 18, 132, 3, 1, 155, 154, 174, 2, 17, 0, 0, 0, 4, 117, 227, 240, 233, 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