Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 404f5bb862444a54acbc3359c81900e4cbc8e07f4b9eef47ad65638301be840f

Tx prefix hash: feae254adb0b76d61d9242032aac455897d4865cdd2047c6b83c7c277823bd48
Tx public key: 1c3f0cefe831430dd5e13e547ef2eab718dbb355980dd6ae02e514abc7a5ce44
Timestamp: 1713285346 Timestamp [UCT]: 2024-04-16 16:35:46 Age [y:d:h:m:s]: 00:269:03:35:31
Block: 1001868 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 192672 RingCT/type: yes/0
Extra: 011c3f0cefe831430dd5e13e547ef2eab718dbb355980dd6ae02e514abc7a5ce4402110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b6f48dd2bbd0f8c0d084f8ca0b2445055059b4015e3cebbc715479cafdb06473 0.600000000000 1462380 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": 1001878, "vin": [ { "gen": { "height": 1001868 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b6f48dd2bbd0f8c0d084f8ca0b2445055059b4015e3cebbc715479cafdb06473" } } ], "extra": [ 1, 28, 63, 12, 239, 232, 49, 67, 13, 213, 225, 62, 84, 126, 242, 234, 183, 24, 219, 179, 85, 152, 13, 214, 174, 2, 229, 20, 171, 199, 165, 206, 68, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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