Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d1457f17b25dde8e4e146d8bf0d2935eee0e3edabc52dcc0de93fa19c8493bbd

Tx prefix hash: 4748570faf9ad2d59101180ceee2564c05cfca77ad1b4e860b6f007c5eefed28
Tx public key: fe2b7c421e6264cb2847c2e9a0eb2c7e362eeb4087f74401630e32c9b58a6fc8
Timestamp: 1714442262 Timestamp [UCT]: 2024-04-30 01:57:42 Age [y:d:h:m:s]: 01:016:05:21:23
Block: 1011471 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 272540 RingCT/type: yes/0
Extra: 01fe2b7c421e6264cb2847c2e9a0eb2c7e362eeb4087f74401630e32c9b58a6fc80211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1400276a62cd72b47f66b5882a659419ed63901311b102790ab33167b144c54f 0.600000000000 1473713 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": 1011481, "vin": [ { "gen": { "height": 1011471 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1400276a62cd72b47f66b5882a659419ed63901311b102790ab33167b144c54f" } } ], "extra": [ 1, 254, 43, 124, 66, 30, 98, 100, 203, 40, 71, 194, 233, 160, 235, 44, 126, 54, 46, 235, 64, 135, 247, 68, 1, 99, 14, 50, 201, 181, 138, 111, 200, 2, 17, 0, 0, 0, 1, 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