Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c58fc54a104ccc6748bea8c3df4bf082e48c2bd3536f8ae36c3f0a17869ec7e1

Tx prefix hash: 78f09e6c090dbc92e78a3586ba350c8474b3cad5cd7895a8e031c8a4543ec5e3
Tx public key: f5e5510465635c4b80af1d321c353030eadd0ef84579e7481e06d327bfa686bb
Timestamp: 1699680539 Timestamp [UCT]: 2023-11-11 05:28:59 Age [y:d:h:m:s]: 01:075:15:11:33
Block: 889096 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 315423 RingCT/type: yes/0
Extra: 01f5e5510465635c4b80af1d321c353030eadd0ef84579e7481e06d327bfa686bb021100000001679a8a81000000000000000000

1 output(s) for total of 0.695113735000 dcy

stealth address amount amount idx
00: 37a419bf7be6fbccabc6e7ffb5c3fdf4cba4d749cf0d57bb34a0408453ed1261 0.695113735000 1345073 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": 889106, "vin": [ { "gen": { "height": 889096 } } ], "vout": [ { "amount": 695113735, "target": { "key": "37a419bf7be6fbccabc6e7ffb5c3fdf4cba4d749cf0d57bb34a0408453ed1261" } } ], "extra": [ 1, 245, 229, 81, 4, 101, 99, 92, 75, 128, 175, 29, 50, 28, 53, 48, 48, 234, 221, 14, 248, 69, 121, 231, 72, 30, 6, 211, 39, 191, 166, 134, 187, 2, 17, 0, 0, 0, 1, 103, 154, 138, 129, 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