Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 75457b84d12040fc2d8d99ff42a557fe529f530e1bb05e82249b60c9d92462a6

Tx prefix hash: 3973710004a5284fb5d58bea70d77030a24640a4c7a40b64ccc1ab515c163e0e
Tx public key: 0432aef4e776c1d0058329bb666db5e84b79dc62c3d84141c6400e73d7e5eca7
Timestamp: 1727406656 Timestamp [UCT]: 2024-09-27 03:10:56 Age [y:d:h:m:s]: 00:195:02:49:05
Block: 1118958 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 139264 RingCT/type: yes/0
Extra: 010432aef4e776c1d0058329bb666db5e84b79dc62c3d84141c6400e73d7e5eca7021100000007e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7a17e9270be072bc23a6e1f9e4b47a79929427d8df3d5c84fdb57f88ab6d8b61 0.600000000000 1600333 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": 1118968, "vin": [ { "gen": { "height": 1118958 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7a17e9270be072bc23a6e1f9e4b47a79929427d8df3d5c84fdb57f88ab6d8b61" } } ], "extra": [ 1, 4, 50, 174, 244, 231, 118, 193, 208, 5, 131, 41, 187, 102, 109, 181, 232, 75, 121, 220, 98, 195, 216, 65, 65, 198, 64, 14, 115, 215, 229, 236, 167, 2, 17, 0, 0, 0, 7, 233, 20, 221, 21, 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