Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f3c5761a6115d3be7de86fb99bb625b9a4caf91cb2558ca500663d5b474f56a0

Tx prefix hash: 7b4160edd0eb274215c9dc1e7f22e6ab20bad0020cd68c7ebf7d04c821f7de22
Tx public key: 4370fc4c9f5fd855f8fb0436712c0cedb7a51f23e92e643d85a17c2f0cefba62
Timestamp: 1681868446 Timestamp [UCT]: 2023-04-19 01:40:46 Age [y:d:h:m:s]: 01:311:22:02:37
Block: 741668 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 484168 RingCT/type: yes/0
Extra: 014370fc4c9f5fd855f8fb0436712c0cedb7a51f23e92e643d85a17c2f0cefba6202110000000175e3f0e9000000000000000000

1 output(s) for total of 2.140652884000 dcy

stealth address amount amount idx
00: fcf246576824bb52c3fbf30b0cae1bfbdb554678b3b7e5da0e7d7c77ee2374fe 2.140652884000 1188603 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": 741678, "vin": [ { "gen": { "height": 741668 } } ], "vout": [ { "amount": 2140652884, "target": { "key": "fcf246576824bb52c3fbf30b0cae1bfbdb554678b3b7e5da0e7d7c77ee2374fe" } } ], "extra": [ 1, 67, 112, 252, 76, 159, 95, 216, 85, 248, 251, 4, 54, 113, 44, 12, 237, 183, 165, 31, 35, 233, 46, 100, 61, 133, 161, 124, 47, 12, 239, 186, 98, 2, 17, 0, 0, 0, 1, 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