Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1f9c296e8bae3f56622c2170a2f370819f47b82b3f1313cf80aa130f10460aa8

Tx prefix hash: bf8012b4eb2698651586c525fb647f2767300c96dee93e81b449f4fe33dd8f05
Tx public key: 0908b4eb4309e9b45aa732f8679cb1c176bda689fb3f9489bc0db2aa5c4b2688
Timestamp: 1720626554 Timestamp [UCT]: 2024-07-10 15:49:14 Age [y:d:h:m:s]: 00:105:10:33:31
Block: 1062754 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 75488 RingCT/type: yes/0
Extra: 010908b4eb4309e9b45aa732f8679cb1c176bda689fb3f9489bc0db2aa5c4b2688021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f2f13c302e9d043ae6ead70511c4f5b6f5c86bff7f9ee81b5be2ea07282e7772 0.600000000000 1533261 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": 1062764, "vin": [ { "gen": { "height": 1062754 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f2f13c302e9d043ae6ead70511c4f5b6f5c86bff7f9ee81b5be2ea07282e7772" } } ], "extra": [ 1, 9, 8, 180, 235, 67, 9, 233, 180, 90, 167, 50, 248, 103, 156, 177, 193, 118, 189, 166, 137, 251, 63, 148, 137, 188, 13, 178, 170, 92, 75, 38, 136, 2, 17, 0, 0, 0, 2, 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