Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fe23a3e3f4a3998b45895ce2092d7644d886eec6853b18ef1abc1e92af8908a8

Tx prefix hash: 620e1d9944e5ab7b792eb3b2d6aa290aca882c5d49a513b367cd2d5c94db7c7a
Tx public key: 7c7276c0ee9dea54235f5413aef1de63f8e0fc3ff4abf6a6a90a8c41d43b226a
Timestamp: 1670633497 Timestamp [UCT]: 2022-12-10 00:51:37 Age [y:d:h:m:s]: 02:335:01:58:06
Block: 649169 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 758903 RingCT/type: yes/0
Extra: 017c7276c0ee9dea54235f5413aef1de63f8e0fc3ff4abf6a6a90a8c41d43b226a0211000000017e406890000000000000000000

1 output(s) for total of 4.335444269000 dcy

stealth address amount amount idx
00: d08d7d0e1ea7df50f9b38cf74fe8a4ec7baf59f3001df3ceb68f1fc30fe9acb6 4.335444269000 1089528 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": 649179, "vin": [ { "gen": { "height": 649169 } } ], "vout": [ { "amount": 4335444269, "target": { "key": "d08d7d0e1ea7df50f9b38cf74fe8a4ec7baf59f3001df3ceb68f1fc30fe9acb6" } } ], "extra": [ 1, 124, 114, 118, 192, 238, 157, 234, 84, 35, 95, 84, 19, 174, 241, 222, 99, 248, 224, 252, 63, 244, 171, 246, 166, 169, 10, 140, 65, 212, 59, 34, 106, 2, 17, 0, 0, 0, 1, 126, 64, 104, 144, 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