Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 727a6dd96546a61880eeb2c2733d9f31e271e69d8d72c5349c365fefa5d53b31

Tx prefix hash: 196689d5b87aefa61afd3f41b05303ccc96be1a47e413ca8222f61f1572617c8
Tx public key: 202d5249e9f2f1e87de4b4a780718d3fbb4509e37e99bea152aea7a63ca5af27
Timestamp: 1676988930 Timestamp [UCT]: 2023-02-21 14:15:30 Age [y:d:h:m:s]: 02:042:14:56:04
Block: 701851 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 552050 RingCT/type: yes/0
Extra: 01202d5249e9f2f1e87de4b4a780718d3fbb4509e37e99bea152aea7a63ca5af2702110000000374b6d784000000000000000000

1 output(s) for total of 2.900522210000 dcy

stealth address amount amount idx
00: 8ac2c3ee49db3666879ba886695ec392f3f026fbbe3db1589148e3079c7de14b 2.900522210000 1145342 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": 701861, "vin": [ { "gen": { "height": 701851 } } ], "vout": [ { "amount": 2900522210, "target": { "key": "8ac2c3ee49db3666879ba886695ec392f3f026fbbe3db1589148e3079c7de14b" } } ], "extra": [ 1, 32, 45, 82, 73, 233, 242, 241, 232, 125, 228, 180, 167, 128, 113, 141, 63, 187, 69, 9, 227, 126, 153, 190, 161, 82, 174, 167, 166, 60, 165, 175, 39, 2, 17, 0, 0, 0, 3, 116, 182, 215, 132, 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